← previous blocknext block →recent activity
Analyzing
Block #90,793,398
16 transactions · 15 stateful · 2026-07-27 14:17:34 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,793,398 · 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
2w03w14w26w07w18w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99b2ea23…110d
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda8d6085…7b09
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x99b2ea2356…cf110d
Audit this contract →
← previous block·next block →recent activity