← previous blocknext block →recent activity
Analyzing
Block #78,362,168
14 transactions · 13 stateful · 2026-06-01 05:52:42 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #78,362,168 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd887c9…e862
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xad8e194d…1e74
0x065c9d…c394
3 touches
1 conflict
0xe02e552a…eaf6
0x065c9d…c394
3 touches
1 conflict
0x85b03987…1bf7
0x2a68ba…90c5
2 touches
1 conflict
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 0xfdd887c90b…f0e862
Audit this contract →
← previous block·next block →recent activity