← previous blocknext block →recent activity
Analyzing
Block #84,365,289
12 transactions · 11 stateful · 2026-06-29 01:27:35 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,365,289 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe181f491…f4e3
0x34b655…2a6f
6 touches
3 conflicts
0x0ee4fe41…9382
0x34b655…2a6f
4 touches
1 conflict
0xd4b3eaed…38c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x3287e4ec…eaa3
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity