← previous blocknext block →recent activity
Analyzing
Block #83,616,244
20 transactions · 17 stateful · 2026-06-25 14:14:23 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,616,244 · 20 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
1w02w03w04w16w010w112w214w015w116w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x250c3574…21db
0x851145…3f07
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xf8ceaa24…6e8e
0x851145…3f07
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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