← previous blocknext block →recent activity
Analyzing
Block #82,269,898
12 transactions · 11 stateful · 2026-06-19 08:20:00 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,269,898 · 12 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
2w03w16w27w38w4
- 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
6 touches
3 conflicts
0xd3e8cf12…cd89
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5328f529…b383
0x065c9d…c394
3 touches
1 conflict
0x85ae75dc…5e9f
0x065c9d…c394
3 touches
1 conflict
0xaf1b999b…e600
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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