← previous blocknext block →recent activity
Analyzing
Block #82,158,952
26 transactions · 24 stateful · 2026-06-18 20:00:16 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,158,952 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x66c5e348…51d0
0xa6afd3…d132
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
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
15 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity