← previous blocknext block →recent activity
Analyzing
Block #87,306,944
13 transactions · 11 stateful · 2026-07-12 16:39:48 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,306,944 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974c36fe…1cd7
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6ba89834…1826
0x34b655…2a6f
6 touches
3 conflicts
0x17fbe072…2ea6
0x34b655…2a6f
4 touches
1 conflict
0x33b5785a…71a2
0x34b655…2a6f
4 touches
1 conflict
0x3bca5b95…9ee9
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a411
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
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
6 conflicts on slot 0x974c36fe03…4f1cd7
Audit this contract →
← previous block·next block →recent activity