← previous blocknext block →recent activity
Analyzing
Block #80,104,284
23 transactions · 17 stateful · 2026-06-09 07:44:10 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,104,284 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x9ff176a9…152e
0x065c9d…c394
12 touches
15 conflicts
0x5540f956…69e8
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
8 touches
6 conflicts
0x98e3c27a…7a3a
0x065c9d…c394
7 touches
6 conflicts
0xaa6d1290…3c56
0x065c9d…c394
7 touches
6 conflicts
0xd0ec60a1…d244
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity