← previous blocknext block →recent activity
Analyzing
Block #90,213,881
12 transactions · 10 stateful · 2026-07-25 13:27:06 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,213,881 · 12 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
1w02w03w15w27w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x78aa5678…e512
0x34b655…2a6f
4 touches
1 conflict
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x58d6b9cf…7c9e
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
1 conflict on slot 0x5af098c77e…e94806
Audit this contract →
← previous block·next block →recent activity