← previous blocknext block →recent activity
Analyzing
Block #84,540,696
22 transactions · 22 stateful · 2026-06-29 20:57:04 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,540,696 · 22 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
1w02w14w05w111w013w114w215w316w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ef8a353…abe4
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xd18a8dca…452e
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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: 0xfa32f9ec…fef3f0
1 conflict on slot 0x5ef8a35338…69abe4
Audit this contract →
← previous block·next block →recent activity