← previous blocknext block →recent activity
Analyzing
Block #86,216,813
13 transactions · 12 stateful · 2026-07-07 15:11:57 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,216,813 · 13 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
3w06w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bad3cdf…d4fb
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x913b7808…7e04
0x34b655…2a6f
4 touches
1 conflict
0x53bad7f6…0db2
0x065c9d…c394
2 touches
0 conflicts
0x53cbf9df…878a
0x065c9d…c394
2 touches
0 conflicts
0x030cdb13…24be
0x34b655…2a6f
2 touches
0 conflicts
0x069b18e0…deae
0x34b655…2a6f
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 0x5bad3cdf66…50d4fb
Audit this contract →
← previous block·next block →recent activity