← previous blocknext block →recent activity
Analyzing
Block #84,598,489
11 transactions · 11 stateful · 2026-06-30 03:22:45 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,598,489 · 11 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
2w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3a4789bf…6358
0x34b655…2a6f
6 touches
3 conflicts
0x344bc09a…942f
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x28a127c8…2b8a
0x34b655…2a6f
2 touches
0 conflicts
0x40b5f387…a164
0x34b655…2a6f
2 touches
0 conflicts
0x4384dd01…4f99
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