← previous blocknext block →recent activity
Analyzing
Block #83,580,781
16 transactions · 14 stateful · 2026-06-25 10:17:35 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,580,781 · 16 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
3w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x557cd4fa…228c
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x29385582…b7d5
0x065c9d…c394
4 touches
1 conflict
0x33d5e675…ef90
0x065c9d…c394
3 touches
1 conflict
0xe2197615…9aa5
0x065c9d…c394
3 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x19ce481d…6c36
0x34b655…2a6f
2 touches
0 conflicts
0x2ac54041…4713
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
3 conflicts on slot 0x557cd4fad5…e4228c
Audit this contract →
← previous block·next block →recent activity