← previous blocknext block →recent activity
Analyzing
Block #87,453,200
12 transactions · 10 stateful · 2026-07-13 08:57:54 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,453,200 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x239122db…dc81
0x34b655…2a6f
6 touches
3 conflicts
0xfec3435f…4a72
0x34b655…2a6f
6 touches
3 conflicts
0x2549dda6…9e24
0x34b655…2a6f
4 touches
1 conflict
0x2bec5ebb…ab7d
0x34b655…2a6f
4 touches
1 conflict
0x015c28a0…37da
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity