← previous blocknext block →recent activity
Analyzing
Block #94,668,683
16 transactions · 10 stateful · 2026-08-10 03:31:00 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,668,683 · 16 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
2w08w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa9c8de66…7266
0x065c9d…c394
4 touches
1 conflict
0xcb29bda0…3b71
0x065c9d…c394
4 touches
1 conflict
0x1f834b10…5be5
0x065c9d…c394
3 touches
1 conflict
0x73b330fc…5ae2
0x065c9d…c394
3 touches
1 conflict
0x3c65046a…6d6d
0x065c9d…c394
3 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity