← previous blocknext block →recent activity
Analyzing
Block #90,688,638
18 transactions · 16 stateful · 2026-07-27 05:30:33 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,688,638 · 18 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
1w02w03w14w09w110w211w112w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5ebff854…1952
0x34b655…2a6f
6 touches
3 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
4 touches
1 conflict
0x38b697c2…c3f3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity