← previous blocknext block →recent activity
Analyzing
Block #91,567,564
15 transactions · 12 stateful · 2026-07-30 07:15:32 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,567,564 · 15 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
2w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc39e7820…76b1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x144a08a1…4585
0x065c9d…c394
3 touches
1 conflict
0x3a202e8a…0029
0x065c9d…c394
3 touches
1 conflict
0xa8ee9f88…9681
0x065c9d…c394
3 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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 0xc39e7820f1…2676b1
Audit this contract →
← previous block·next block →recent activity