← previous blocknext block →recent activity
Analyzing
Block #97,844,415
30 transactions · 26 stateful · 2026-08-21 07:03:03 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,844,415 · 30 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
1w02w15w07w08w110w011w112w114w015w016w117w218w219w120w223w324w329w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8b2aa7d…875e
0x065c9d…c394
7 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xc8b2aa7d69…38875e
Audit this contract →
← previous block·next block →recent activity