← previous blocknext block →recent activity
Analyzing
Block #86,332,121
17 transactions · 16 stateful · 2026-07-08 04:01:57 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,332,121 · 17 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
2w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d537073…cf27
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x4a910dc0…2ed6
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xf2b84e4b…d15b
0x065c9d…c394
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 0x5d537073f1…d2cf27
Audit this contract →
← previous block·next block →recent activity