← previous blocknext block →recent activity
Analyzing
Block #84,335,595
22 transactions · 16 stateful · 2026-06-28 22:09:34 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,335,595 · 22 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
10w011w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c119c6d…a42e
0x34b655…2a6f
4 touches
1 conflict
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0x91673ce7…6af9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0xf7468e81…86e5
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x153beb2d…a455
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 0x0c119c6d6d…e8a42e
Audit this contract →
← previous block·next block →recent activity