← previous blocknext block →recent activity
Analyzing
Block #86,320,129
19 transactions · 16 stateful · 2026-07-08 02:41:52 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,320,129 · 19 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
1w02w13w26w17w08w111w013w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1a8fa07…8b78
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0000
0x16d564…365f
4 touches
1 conflict
0x00000000…0002
0x16d564…365f
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0x07dfab5d…064d
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity