← previous blocknext block →recent activity
Analyzing
Block #86,981,224
9 transactions · 5 stateful · 2026-07-11 04:22:08 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,981,224 · 9 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
1w02w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
0x34b655…2a6f
4 touches
1 conflict
0xf93a792c…7efc
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0xd65c308c…edfe
0x40c49f…2af0
2 touches
0 conflicts
0xef3f6769…4310
0x40c49f…2af0
2 touches
0 conflicts
0xfd7c84af…cd8d
0x40c49f…2af0
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 0x5b37bb6bbf…0aab00
Audit this contract →
← previous block·next block →recent activity