← previous blocknext block →recent activity
Analyzing
Block #90,045,402
9 transactions · 9 stateful · 2026-07-24 23:15:01 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,045,402 · 9 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
2w03w14w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89935301…af69
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x3055b4d0…81c0
0x34b655…2a6f
4 touches
1 conflict
0x4c702894…9f4c
0x34b655…2a6f
4 touches
1 conflict
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0x6d74089c…c836
0x34b655…2a6f
4 touches
1 conflict
0x79963e73…50be
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
3 conflicts on slot 0x8993530124…aaaf69
Audit this contract →
← previous block·next block →recent activity