← previous blocknext block →recent activity
Analyzing
Block #87,453,182
13 transactions · 13 stateful · 2026-07-13 08:57:47 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,453,182 · 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
7w08w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x239122db…dc81
0x34b655…2a6f
6 touches
3 conflicts
0x47e8b6f8…8bb3
0x34b655…2a6f
4 touches
1 conflict
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0x0645d537…1ce4
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0x4814529d…5f07
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity