← previous blocknext block →recent activity
Analyzing
Block #90,552,662
9 transactions · 9 stateful · 2026-07-26 18:06:29 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,552,662 · 9 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0x206ed0b7…7ee9
0x34b655…2a6f
4 touches
1 conflict
0x0d336deb…3fee
0x34b655…2a6f
2 touches
0 conflicts
0x10c54b98…bbcf
0x34b655…2a6f
2 touches
0 conflicts
0x1730ab3c…ce37
0x34b655…2a6f
2 touches
0 conflicts
0x17ece76b…2cab
0x34b655…2a6f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity