← previous blocknext block →recent activity
Analyzing
Block #87,456,223
15 transactions · 14 stateful · 2026-07-13 09:18:08 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,456,223 · 15 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
4w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x066dac8a…ac86
0x34b655…2a6f
4 touches
1 conflict
0x0e367fee…d4bc
0x34b655…2a6f
4 touches
1 conflict
0x0e367fee…d4bd
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb37
0x34b655…2a6f
4 touches
1 conflict
0x6b55f7df…5bc5
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: Perpl
1 conflict on slot 0x066dac8aa1…c2ac86
Audit this contract →
← previous block·next block →recent activity