← previous blocknext block →recent activity
Analyzing
Block #84,141,051
14 transactions · 12 stateful · 2026-06-28 00:33:42 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,141,051 · 14 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
1w03w04w15w26w37w310w111w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38ec2c24…ef42
0x34b655…2a6f
8 touches
6 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
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
6 conflicts on slot 0x38ec2c2452…0aef42
Audit this contract →
← previous block·next block →recent activity