← previous blocknext block →recent activity
Analyzing
Block #90,639,307
11 transactions · 9 stateful · 2026-07-27 01:22:22 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,639,307 · 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
2w03w14w15w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xf3a729aa…6665
0x34b655…2a6f
4 touches
1 conflict
0x1fdc16cf…015e
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0xe2a69c1c…c9b0
0x34b655…2a6f
4 touches
1 conflict
0xc9f7b83f…a184
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7b
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: Perpl
1 conflict on slot 0xc824469a90…af641e
Audit this contract →
← previous block·next block →recent activity