← previous blocknext block →recent activity
Analyzing
Block #83,201,002
18 transactions · 15 stateful · 2026-06-23 16:01:49 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,201,002 · 18 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
1w02w13w04w18w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x67a58201…1968
0xa6afd3…d132
3 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x2ae779cb…3839
0x065c9d…c394
2 touches
0 conflicts
0x318105aa…a716
0x065c9d…c394
2 touches
0 conflicts
0x776771db…fb42
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity