← previous blocknext block →recent activity
Analyzing
Block #90,232,709
14 transactions · 13 stateful · 2026-07-25 15:02:03 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,232,709 · 14 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
1w02w14w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xaaab9ccd…e3c7
0x40c49f…2af0
3 touches
1 conflict
0xa0bab64e…b8c0
0x080ec9…fe74
2 touches
0 conflicts
0x00000000…0008
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…0009
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…000a
0x14c8e4…fdcb
2 touches
0 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: Kuru Exchange: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity