← previous blocknext block →recent activity
Analyzing
Block #90,043,627
11 transactions · 10 stateful · 2026-07-24 23:06:04 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,043,627 · 11 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
6w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2da28f3b…cc6e
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x18316bb4…d507
0x34b655…2a6f
4 touches
1 conflict
0x48e336e0…145d
0x065c9d…c394
2 touches
0 conflicts
0x7a43e95d…f3d7
0x065c9d…c394
2 touches
0 conflicts
0xb1f9a088…d5bf
0x065c9d…c394
2 touches
0 conflicts
0xe1fdc03e…ffd5
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: Perpl
1 conflict on slot 0x2da28f3b58…b9cc6e
Audit this contract →
← previous block·next block →recent activity