← previous blocknext block →recent activity
Analyzing
Block #90,623,428
13 transactions · 12 stateful · 2026-07-27 00:02:29 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,623,428 · 13 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
5w06w18w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x1fdc16cf…015e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
0x34b655…2a6f
2 touches
0 conflicts
0x7b0665e8…fbdf
0x34b655…2a6f
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 0x5b6af0070f…160f35
Audit this contract →
← previous block·next block →recent activity