← previous blocknext block →recent activity
Analyzing
Block #90,791,449
16 transactions · 15 stateful · 2026-07-27 14:07:46 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,791,449 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62dbeb4d…a388
0x34b655…2a6f
8 touches
6 conflicts
0x467e4e45…3eb6
0x34b655…2a6f
6 touches
3 conflicts
0x5f5a0edf…ebcc
0x34b655…2a6f
6 touches
3 conflicts
0x16216d99…518a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe6797d63…ab07
0x34b655…2a6f
6 touches
3 conflicts
0x69c491e3…98d9
0x34b655…2a6f
6 touches
3 conflicts
0x0a005879…de60
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
6 conflicts on slot 0x62dbeb4d5d…05a388
Audit this contract →
← previous block·next block →recent activity