← previous blocknext block →recent activity
Analyzing
Block #93,407,129
11 transactions · 10 stateful · 2026-08-05 17:30:41 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,407,129 · 11 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a69cbc2…adb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc1bc5cff…5223
0x065c9d…c394
3 touches
1 conflict
0x7e8e8faf…b315
0x065c9d…c394
3 touches
1 conflict
0x8b258f69…3a41
0x065c9d…c394
3 touches
1 conflict
0x9aad771d…1e27
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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 0x4a69cbc22e…2dadb3
Audit this contract →
← previous block·next block →recent activity