← previous blocknext block →recent activity
Analyzing
Block #90,026,236
10 transactions · 9 stateful · 2026-07-24 21:38:26 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,026,236 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x373e37bf…c293
0x0a2fbf…29b1
4 touches
1 conflict
0x8a7942ff…9cc3
0x0a2fbf…29b1
4 touches
1 conflict
0x8a7942ff…9cc4
0x0a2fbf…29b1
4 touches
1 conflict
0x8a7942ff…9cc7
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0xf73a62d4…6ad7
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
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: 0x0a2fbf2d…f729b1
1 conflict on slot 0x373e37bf32…c1c293
Audit this contract →
← previous block·next block →recent activity