← previous blocknext block →recent activity
Analyzing
Block #84,021,393
21 transactions · 17 stateful · 2026-06-27 11:16:42 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,021,393 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w09w010w111w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f8e890…a736
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x28f56c4e…c953
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x60431a53…da00
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xa4f8e890b1…8da736
Audit this contract →
← previous block·next block →recent activity