← previous blocknext block →recent activity
Analyzing
Block #84,572,966
23 transactions · 20 stateful · 2026-06-30 00:32:45 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,572,966 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w17w28w39w016w317w318w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0xca3931f0…0855
0x34b655…2a6f
4 touches
1 conflict
0x0c969dde…6b06
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x29686688…0598
0xa6afd3…d132
4 touches
1 conflict
0x2ae1288a…2b44
0xd32edf…ff58
3 touches
1 conflict
0x3d0ee625…932e
0xa6afd3…d132
3 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity