← previous blocknext block →recent activity
Analyzing
Block #84,572,669
24 transactions · 19 stateful · 2026-06-30 00:30:47 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,572,669 · 24 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
2w07w08w19w010w114w018w119w220w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xb44d5376…33cc
0x34b655…2a6f
4 touches
1 conflict
0xbc9aaf19…8cfd
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa307c334…c9ae
0x754704…b603
4 touches
1 conflict
0xd131506e…b74b
0x754704…b603
4 touches
1 conflict
0x3f75fb9e…0d2e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity