← previous blocknext block →recent activity
Analyzing
Block #87,361,525
18 transactions · 17 stateful · 2026-07-12 22:44:47 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,361,525 · 18 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
1w02w14w05w16w210w111w212w113w214w316w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x0090639e…243e
0x34b655…2a6f
4 touches
1 conflict
0x18ec97d9…6baa
0x34b655…2a6f
4 touches
1 conflict
0x27a78688…b891
0x34b655…2a6f
4 touches
1 conflict
0x7a916b05…8a00
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1ac
Audit this contract →
← previous block·next block →recent activity