← previous blocknext block →recent activity
Analyzing
Block #102,011,744
19 transactions · 18 stateful · 2026-09-04 21:51:32 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,011,744 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w213w014w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
6 touches
3 conflicts
0x7fd951f1…fe49
0x34b655…2a6f
6 touches
3 conflicts
0x898a08aa…c855
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x024b482b…16b0
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
3 conflicts on slot 0xeb1b66a1ed…55ce4e
Audit this contract →
← previous block·next block →recent activity