← previous blocknext block →recent activity
Analyzing
Block #93,326,687
13 transactions · 12 stateful · 2026-08-05 10:46:14 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,326,687 · 13 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
2w05w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xc5092e17…732f
0x065c9d…c394
3 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x3745e2ac…1d97
0x34b655…2a6f
2 touches
0 conflicts
0x4f1e16d4…4833
0x34b655…2a6f
2 touches
0 conflicts
0x560b6fd9…a104
0x34b655…2a6f
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