← previous blocknext block →recent activity
Analyzing
Block #90,636,692
15 transactions · 14 stateful · 2026-07-27 01:09:13 UTC
Parallelism
53/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,636,692 · 15 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
2w03w14w25w36w47w08w19w510w611w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cab9ea4…924f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe8d58d34…426d
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xbb322930…ace5
0x34b655…2a6f
6 touches
3 conflicts
0x9c166a56…0356
0x34b655…2a6f
4 touches
1 conflict
0xa15e2d91…025a
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
10 conflicts on slot 0x0cab9ea4ff…32924f
Audit this contract →
← previous block·next block →recent activity