← previous blocknext block →recent activity
Analyzing
Block #87,362,256
7 transactions · 6 stateful · 2026-07-12 22:49:41 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,362,256 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3a31d1…7a6e
0x34b655…2a6f
4 touches
1 conflict
0x6b4a1723…ed53
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6d
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6e
0x34b655…2a6f
4 touches
1 conflict
0x76b3ccc8…64f4
0x34b655…2a6f
4 touches
1 conflict
0x5bf60f1c…3394
0x34b655…2a6f
4 touches
1 conflict
0x5dccc158…65de
0x34b655…2a6f
4 touches
1 conflict
0x218485e2…8f57
0x34b655…2a6f
3 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: Perpl
1 conflict on slot 0x5e3a31d155…bb7a6e
Audit this contract →
← previous block·next block →recent activity