← previous blocknext block →recent activity
Analyzing
Block #84,254,251
10 transactions · 10 stateful · 2026-06-28 13:07:38 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,254,251 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x31a4cbfd…23a9
0x34b655…2a6f
2 touches
0 conflicts
0x393dfd73…ff57
0x34b655…2a6f
2 touches
0 conflicts
0x921a58d1…db22
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
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
3 conflicts on slot 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity