← previous blocknext block →recent activity
Analyzing
Block #90,301,429
17 transactions · 14 stateful · 2026-07-25 20:49:34 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,301,429 · 17 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
3w04w05w16w07w19w211w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3b3d00…18cf
0x0a2fbf…29b1
8 touches
6 conflicts
0x9a3b3d00…18d0
0x0a2fbf…29b1
8 touches
6 conflicts
0xd623eb83…7bc6
0x0a2fbf…29b1
8 touches
6 conflicts
0xd623eb83…7bc7
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x35f6c38c…f5fc
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0xd623eb83…7bca
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 0x9a3b3d00ec…4e18cf
Audit this contract →
← previous block·next block →recent activity