← previous blocknext block →recent activity
Analyzing
Block #86,227,487
18 transactions · 15 stateful · 2026-07-07 16:23:11 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,227,487 · 18 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
5w06w17w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x040f5870…c505
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe4a7d12c…58ae
0x34b655…2a6f
3 touches
1 conflict
0x7f6defda…23fd
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0xf82ced13…84c6
0x2a68ba…90c5
2 touches
0 conflicts
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 0x040f587093…22c505
Audit this contract →
← previous block·next block →recent activity