← previous blocknext block →recent activity
Analyzing
Block #87,513,447
18 transactions · 15 stateful · 2026-07-13 15:40:54 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,513,447 · 18 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
2w03w16w28w09w110w211w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x18ca6535…87c1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x93f5e791…a98d
0x34b655…2a6f
6 touches
3 conflicts
0xe20a9313…c20a
0x34b655…2a6f
6 touches
3 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x32e8b881…247b
0x34b655…2a6f
4 touches
1 conflict
0x3f85f288…7c97
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity