← previous blocknext block →recent activity
Analyzing
Block #78,362,507
9 transactions · 7 stateful · 2026-06-01 05:54:56 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #78,362,507 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x739e1726…1da2
0x065c9d…c394
4 touches
1 conflict
0x0615387d…5c26
0x065c9d…c394
3 touches
1 conflict
0x2dd55b4b…3b50
0x065c9d…c394
2 touches
0 conflicts
0x7fc80418…ef0e
0x065c9d…c394
2 touches
0 conflicts
0xcf20f25b…bb82
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity