← previous blocknext block →recent activity
Analyzing
Block #87,612,332
15 transactions · 12 stateful · 2026-07-14 02:42:56 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,612,332 · 15 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
2w07w08w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xcfcb8911…e9da
0x34b655…2a6f
6 touches
3 conflicts
0x12198d2b…3592
0x34b655…2a6f
4 touches
1 conflict
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0x2a704897…c32b
0x34b655…2a6f
4 touches
1 conflict
0x564d127d…5e3f
0x34b655…2a6f
4 touches
1 conflict
0x72561c12…0af0
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