← previous blocknext block →recent activity
Analyzing
Block #79,421,881
12 transactions · 11 stateful · 2026-06-06 03:42:24 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,421,881 · 12 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa82505aa…8037
0x065c9d…c394
3 touches
1 conflict
0xd252cf94…5abf
0x065c9d…c394
3 touches
1 conflict
0x07659393…be12
0x065c9d…c394
3 touches
1 conflict
0x510a79c6…a56a
0x065c9d…c394
3 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xa82505aa8b…528037
Audit this contract →
← previous block·next block →recent activity