← previous blocknext block →recent activity
Analyzing
Block #84,347,063
14 transactions · 13 stateful · 2026-06-28 23:25:59 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,347,063 · 14 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
5w06w17w28w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1a069146…5c12
0x0c65a0…0852
2 touches
0 conflicts
0x2ed6e329…5e08
0x0c65a0…0852
2 touches
0 conflicts
0x0d9c8af7…06a2
0x3bd359…433a
2 touches
0 conflicts
0x6b540c43…c2d5
0x3bd359…433a
2 touches
0 conflicts
0x23cc7c34…6f07
0x754704…b603
2 touches
0 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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity