← previous blocknext block →recent activity
Analyzing
Block #83,029,309
32 transactions · 23 stateful · 2026-06-22 20:53:32 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,029,309 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w011w112w213w315w117w225w428w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x13e72c03…6894
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x5a3732cb…edb3
0x1b6862…e19c
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x8041b0c8…e4e9
0x5afd3e…7620
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
10 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity