← previous blocknext block →recent activity
Analyzing
Block #84,537,859
23 transactions · 21 stateful · 2026-06-29 20:38:09 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,537,859 · 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
3w04w15w26w37w416w017w118w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0002
0x019883…2a9a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
6 touches
3 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
6 touches
3 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
6 touches
3 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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity