← previous blocknext block →recent activity
Analyzing
Block #83,467,504
18 transactions · 18 stateful · 2026-06-24 21:42:15 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,467,504 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w210w212w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
0xa4fad3cd…3f0f
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xea121231…8500
0xa6afd3…d132
5 touches
3 conflicts
0x89fa3104…8020
0x34b655…2a6f
4 touches
1 conflict
0x9603d13f…d632
0x34b655…2a6f
4 touches
1 conflict
0x9610cea3…6614
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity