← previous blocknext block →recent activity
Analyzing
Block #90,039,284
16 transactions · 16 stateful · 2026-07-24 22:44:07 UTC
Parallelism
50/100
Blocked
63%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,039,284 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w39w410w511w612w713w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27cb5857…0714
0x0a2fbf…29b1
16 touches
28 conflicts
0x29312f48…7610
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0005
0x370e2e…63b4
16 touches
28 conflicts
0x29312f48…7614
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0006
0x0a2fbf…29b1
16 touches
28 conflicts
0x27cb5857…0713
0x0a2fbf…29b1
16 touches
28 conflicts
0x55b4e430…44cb
0x754704…b603
16 touches
28 conflicts
0x1bff683e…7ecb
0x754704…b603
16 touches
28 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: 0x0a2fbf2d…f729b1
28 conflicts on slot 0x27cb585792…060714
Audit this contract →
← previous block·next block →recent activity