← previous blocknext block →recent activity
Analyzing
Block #84,025,389
33 transactions · 19 stateful · 2026-06-27 11:43:18 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,025,389 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w111w218w019w120w221w322w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0xe8370d49…b810
0x34b655…2a6f
10 touches
10 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
10 touches
10 conflicts
0x2aab0897…78f7
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xb1b9054c…38fc
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity