← previous blocknext block →recent activity
Analyzing
Block #90,623,759
33 transactions · 27 stateful · 2026-07-27 00:04:09 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,623,759 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w19w010w211w114w016w017w118w219w020w121w222w325w426w028w129w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0xfdfd44a2…b364
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe0bf6f7a…a4b4
0x34b655…2a6f
6 touches
3 conflicts
0xef588c47…4899
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 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
6 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity