← previous blocknext block →recent activity
Analyzing
Block #86,493,038
16 transactions · 16 stateful · 2026-07-08 21:57:20 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,493,038 · 16 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
2w03w14w27w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d37ee…6e67
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0x1d3b8ae2…d6f0
0x34b655…2a6f
10 touches
10 conflicts
0x9379391f…caa2
0x34b655…2a6f
6 touches
3 conflicts
0x0a49c44b…4b7f
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153b
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
10 conflicts on slot 0xfe3d37ee7e…836e67
Audit this contract →
← previous block·next block →recent activity