← previous blocknext block →recent activity
Analyzing
Block #84,428,395
13 transactions · 13 stateful · 2026-06-29 08:28:08 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,428,395 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x14142821…52f6
0xa6afd3…d132
3 touches
1 conflict
0x3f79a18a…6ca2
0xd32edf…ff58
3 touches
1 conflict
0x08b8e539…b9f9
0x754704…b603
2 touches
0 conflicts
0x11622504…ed25
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0x6f58168d48…e3ea24
Audit this contract →
← previous block·next block →recent activity