← previous blocknext block →recent activity
Analyzing
Block #84,528,781
17 transactions · 16 stateful · 2026-06-29 19:37:37 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,528,781 · 17 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
2w03w14w25w36w49w010w111w012w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x659bf1d4…2024
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0xe33999aa…8e37
0x8d1565…6723
10 touches
10 conflicts
0x2780d85d…e961
0x8d1565…6723
10 touches
10 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0xfc111d09…525a
0x336ed4…c59c
10 touches
10 conflicts
0x655939a8…0b3b
0x336ed4…c59c
10 touches
10 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: 0x336ed437…cfc59c
10 conflicts on slot 0x659bf1d4ae…002024
Audit this contract →
← previous block·next block →recent activity