← previous blocknext block →recent activity
Analyzing
Block #78,363,178
10 transactions · 7 stateful · 2026-06-01 05:59:24 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #78,363,178 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x78a42428…b3f1
0x065c9d…c394
3 touches
1 conflict
0x28f09725…2a4e
0x065c9d…c394
3 touches
1 conflict
0x108de796…acfe
0x065c9d…c394
3 touches
1 conflict
0x4f9a2265…2d75
0x065c9d…c394
2 touches
0 conflicts
0x606a0be2…6bad
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
1 conflict on slot 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity