← previous blocknext block →recent activity
Analyzing
Block #84,064,132
22 transactions · 21 stateful · 2026-06-27 16:01:23 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,064,132 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
16 touches
28 conflicts
0x00000000…000a
0x90c374…be45
16 touches
28 conflicts
0x2a9f9737…d07d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd406be52…9094
0x34b655…2a6f
6 touches
3 conflicts
0x7c9d8f66…dee0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x49ddbdb2…7653
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: 0x90c3747c…0ebe45
28 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity