← previous blocknext block →recent activity
Analyzing
Block #79,241,143
18 transactions · 14 stateful · 2026-06-05 07:33:32 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,241,143 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
8 touches
6 conflicts
0x7682c8bd…4d5f
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x36a2326a…d82b
0x065c9d…c394
2 touches
0 conflicts
0x49898b74…8f5d
0x065c9d…c394
2 touches
0 conflicts
0xb3809ff4…80f7
0x065c9d…c394
2 touches
0 conflicts
0xe3ea8a22…6b96
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity