← previous blocknext block →recent activity
Analyzing
Block #93,268,175
28 transactions · 21 stateful · 2026-08-05 05:52:03 UTC
Parallelism
93/100
Blocked
10%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,268,175 · 28 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
1w017w124w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x5f18818d…1672
0x065c9d…c394
3 touches
1 conflict
0x037483c4…5d17
0x065c9d…c394
3 touches
1 conflict
0x1bcd71d5…f83e
0x065c9d…c394
3 touches
1 conflict
0xa8418d31…4ca2
0x065c9d…c394
3 touches
1 conflict
0x19404ef1…131c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity