← previous blocknext block →recent activity
Analyzing
Block #90,499,903
16 transactions · 16 stateful · 2026-07-26 13:41:07 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,499,903 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w28w39w410w513w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0728ec77…146c
0x34b655…2a6f
6 touches
3 conflicts
0x190a8688…7abe
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb45d7b7d…0271
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
15 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity