← previous blocknext block →recent activity
Analyzing
Block #90,238,453
18 transactions · 16 stateful · 2026-07-25 15:30:58 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,238,453 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w08w19w210w311w113w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23949d66…c877
0x0a2fbf…29b1
8 touches
6 conflicts
0x8cb37d47…b473
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x23949d66…c878
0x0a2fbf…29b1
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0x8cb37d47…b474
0x0a2fbf…29b1
8 touches
6 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
6 conflicts on slot 0x23949d66e8…c7c877
Audit this contract →
← previous block·next block →recent activity