← previous blocknext block →recent activity
Analyzing
Block #83,854,163
10 transactions · 9 stateful · 2026-06-26 16:42:07 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,854,163 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7c5260f4…bd96
0xa6afd3…d132
4 touches
1 conflict
0x50f4d4e6…dd21
0x34b655…2a6f
2 touches
0 conflicts
0x5c0393a4…8b86
0x34b655…2a6f
2 touches
0 conflicts
0x5fad6fee…7714
0x34b655…2a6f
2 touches
0 conflicts
0x6047479e…9948
0x34b655…2a6f
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity