← previous blocknext block →recent activity
Analyzing
Block #94,752,132
22 transactions · 16 stateful · 2026-08-10 10:32:00 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,752,132 · 22 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
1w06w17w010w112w014w115w216w217w018w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09f0e4e5…8f3a
0x065c9d…c394
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x62efcbc7…c7e7
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
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
1 conflict on slot 0x09f0e4e5a5…1b8f3a
Audit this contract →
← previous block·next block →recent activity