← previous blocknext block →recent activity
Analyzing
Block #87,723,165
18 transactions · 17 stateful · 2026-07-14 15:04:15 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,723,165 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w111w212w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55aabd7…cdfd
0x34b655…2a6f
6 touches
3 conflicts
0xbfb7adca…51d7
0x34b655…2a6f
6 touches
3 conflicts
0x9aa29e0c…eb5b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x53f72244…23fc
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b643
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b644
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0xa55aabd704…3ccdfd
Audit this contract →
← previous block·next block →recent activity