← previous blocknext block →recent activity
Analyzing
Block #96,825,850
26 transactions · 18 stateful · 2026-08-17 16:38:48 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,825,850 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w113w015w020w123w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc5d41d8…5cdb
0x065c9d…c394
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
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 0xfc5d41d8db…3c5cdb
Audit this contract →
← previous block·next block →recent activity