← previous blocknext block →recent activity
Analyzing
Block #90,044,300
15 transactions · 14 stateful · 2026-07-24 23:09:28 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,044,300 · 15 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
2w03w17w08w19w210w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0xdcc55824…23d1
0x0a2fbf…29b1
6 touches
3 conflicts
0xdcc55824…23d2
0x0a2fbf…29b1
6 touches
3 conflicts
0xdcc55824…23d5
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x1cdf1b48…9f5e
0x34b655…2a6f
4 touches
1 conflict
0x22af2208…099e
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity