← previous blocknext block →recent activity
Analyzing
Block #90,645,096
15 transactions · 13 stateful · 2026-07-27 01:51:29 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,645,096 · 15 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
1w03w05w16w07w18w09w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7badc5e…8c2b
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xef810d4c…d327
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x0e3b59e9…d9d0
0x34b655…2a6f
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-WETH/USDC
1 conflict on slot 0xd7badc5ea1…be8c2b
Audit this contract →
← previous block·next block →recent activity