← previous blocknext block →recent activity
Analyzing
Block #87,737,758
12 transactions · 10 stateful · 2026-07-14 16:41:52 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,737,758 · 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
2w03w17w010w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
8 touches
6 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
6 touches
3 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
4 touches
1 conflict
0x5678673a…57ba
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
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 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity