← previous blocknext block →recent activity
Analyzing
Block #86,958,688
19 transactions · 19 stateful · 2026-07-11 01:51:34 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,958,688 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w09w116w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x008accc4…1da8
0x34b655…2a6f
4 touches
1 conflict
0x1026db44…56c1
0x34b655…2a6f
4 touches
1 conflict
0x166c9cd3…0b58
0x34b655…2a6f
4 touches
1 conflict
0x230a3fb0…e64c
0x34b655…2a6f
4 touches
1 conflict
0x3a4c967a…5e7a
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0x008accc476…b51da7
Audit this contract →
← previous block·next block →recent activity