← previous blocknext block →recent activity
Analyzing
Block #90,704,917
15 transactions · 15 stateful · 2026-07-27 06:52:26 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,704,917 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d38cdb…b9d1
0x34b655…2a6f
6 touches
3 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x53d6f1c9…16c4
0x34b655…2a6f
4 touches
1 conflict
0x65398157…785c
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
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 0xf0d38cdbfd…e9b9d1
Audit this contract →
← previous block·next block →recent activity