← previous blocknext block →recent activity
Analyzing
Block #84,335,400
35 transactions · 28 stateful · 2026-06-28 22:08:16 UTC
Parallelism
89/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,335,400 · 35 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
1w05w06w17w28w39w110w213w018w019w120w223w124w325w126w230w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0e82f095…cb44
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe15c0bf4…d249
0xd32edf…ff58
5 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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity