← previous blocknext block →recent activity
Analyzing
Block #84,527,401
15 transactions · 15 stateful · 2026-06-29 19:28:26 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,527,401 · 15 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
1w02w03w14w25w36w110w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0x74ae383e…8658
0x8d1565…6723
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0xbdc4c820…81a1
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x655939a8…0b3b
0x336ed4…c59c
6 touches
3 conflicts
0x2ad23c92…4745
0x336ed4…c59c
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0x8d156514…236723
6 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity