← previous blocknext block →recent activity
Analyzing
Block #87,723,159
14 transactions · 13 stateful · 2026-07-14 15:04:12 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,723,159 · 14 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
1w02w03w15w16w28w39w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55aabd7…cdfd
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3cfe4586…0bd9
0x34b655…2a6f
4 touches
1 conflict
0xf1ca1c7c…2684
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xa55aabd704…3ccdfd
Audit this contract →
← previous block·next block →recent activity