← previous blocknext block →recent activity
Analyzing
Block #90,287,961
14 transactions · 13 stateful · 2026-07-25 19:41:05 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,287,961 · 14 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
1w03w04w16w17w08w19w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x158401b3…d391
0x0a2fbf…29b1
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x158401b3…d392
0x0a2fbf…29b1
6 touches
3 conflicts
0xb10db32e…d5da
0x0a2fbf…29b1
6 touches
3 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
3 conflicts on slot 0x158401b3a6…bbd391
Audit this contract →
← previous block·next block →recent activity