← previous blocknext block →recent activity
Analyzing
Block #84,034,041
10 transactions · 8 stateful · 2026-06-27 12:40:51 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,034,041 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0x3356c74d…6a23
0x34b655…2a6f
4 touches
1 conflict
0xd140b64a…32f2
0x34b655…2a6f
3 touches
1 conflict
0xaf4ecd21…04f9
0x000000…012a
2 touches
0 conflicts
0x52c63247…ce02
0x103222…7496
2 touches
0 conflicts
0x0b87c369…67ce
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
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 0xb99958f6c8…c6ccf0
Audit this contract →
← previous block·next block →recent activity