← previous blocknext block →recent activity
Analyzing
Block #93,446,716
17 transactions · 16 stateful · 2026-08-05 20:49:43 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,446,716 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w18w39w010w111w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x210e4372…eee3
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x4cb3f181…31aa
0x065c9d…c394
5 touches
3 conflicts
0x595c124e…594e
0x065c9d…c394
5 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0x8e98ed18…fc36
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x210e437280…a3eee3
Audit this contract →
← previous block·next block →recent activity