← previous blocknext block →recent activity
Analyzing
Block #90,463,029
16 transactions · 15 stateful · 2026-07-26 10:35:34 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,463,029 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf3a5784b…1b60
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x02f1d2b3…fb38
0x447d2e…e9f5
2 touches
0 conflicts
0x2506f9b1…6e68
0x447d2e…e9f5
2 touches
0 conflicts
0x255795a7…8377
0x447d2e…e9f5
2 touches
0 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
1 conflict on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity