← previous blocknext block →recent activity
Analyzing
Block #90,637,923
19 transactions · 16 stateful · 2026-07-27 01:15:25 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,637,923 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w09w110w211w113w314w415w216w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xe2e52e4663…6f0894
Audit this contract →
← previous block·next block →recent activity