← previous blocknext block →recent activity
Analyzing
Block #83,577,312
7 transactions · 6 stateful · 2026-06-25 09:54:31 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,577,312 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cd6928f…1a19
0x2a68ba…90c5
4 touches
1 conflict
0xea9f9567…d19e
0xa6afd3…d132
4 touches
1 conflict
0x6a120d89…4b2d
0xa6afd3…d132
3 touches
1 conflict
0xf11e6955…8031
0xa6afd3…d132
3 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x64130037…4ea0
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
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 0x4cd6928f0d…fd1a19
Audit this contract →
← previous block·next block →recent activity