← previous blocknext block →recent activity
Analyzing
Block #105,856,900
21 transactions · 18 stateful · 2026-09-18 09:35:48 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,856,900 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w010w111w212w313w414w515w016w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00e3ad8d…76a8
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
8 touches
6 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xfbd35b2d…47bf
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x00e3ad8d71…6876a8
Audit this contract →
← previous block·next block →recent activity