← previous blocknext block →recent activity
Analyzing
Block #96,045,504
14 transactions · 13 stateful · 2026-08-14 23:13:40 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,045,504 · 14 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
2w03w14w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x042c4359…628d
0x34b655…2a6f
4 touches
1 conflict
0x4174fdf9…fcfd
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x1033aa27…7cab
0xa6afd3…d132
3 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
2 touches
0 conflicts
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-WETH/USDC
1 conflict on slot 0xf219f7cff4…0f7379
Audit this contract →
← previous block·next block →recent activity