← previous blocknext block →recent activity
Analyzing
Block #90,961,915
13 transactions · 12 stateful · 2026-07-28 04:25:24 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,961,915 · 13 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
2w03w04w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x6a3d2f4f…4ad5
0xa6afd3…d132
3 touches
1 conflict
0x788d06b7…0d89
0xa6afd3…d132
3 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
1 conflict on slot 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity