← previous blocknext block →recent activity
Analyzing
Block #90,514,954
10 transactions · 10 stateful · 2026-07-26 14:56:49 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,514,954 · 10 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
1w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x4466522f…d1f3
0x065c9d…c394
2 touches
0 conflicts
0x49898b74…8f5d
0x065c9d…c394
2 touches
0 conflicts
0x855668e9…5fa9
0x065c9d…c394
2 touches
0 conflicts
0xb18006ec…0adf
0x065c9d…c394
2 touches
0 conflicts
0xb855880d…e0ec
0x065c9d…c394
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-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity