← previous blocknext block →recent activity
Analyzing
Block #84,525,925
17 transactions · 17 stateful · 2026-06-29 19:18:36 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,525,925 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w113w214w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb6c88e49…7bbf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x1c5fbdad…9aa5
0x1efe02…37d6
2 touches
0 conflicts
0x244fd533…2236
0x1efe02…37d6
2 touches
0 conflicts
0x4524699c…80d2
0x1efe02…37d6
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity