← previous blocknext block →recent activity
Analyzing
Block #90,603,770
7 transactions · 7 stateful · 2026-07-26 22:23:35 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,603,770 · 7 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf68b5d2…0eba
0x34b655…2a6f
4 touches
1 conflict
0xcbdd47f9…7dcd
0x34b655…2a6f
4 touches
1 conflict
0xcbdd47f9…7dce
0x34b655…2a6f
4 touches
1 conflict
0xcbe863a2…b2dd
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf04729b9…9bc2
0x34b655…2a6f
4 touches
1 conflict
0xf18906a6…d2e3
0x34b655…2a6f
4 touches
1 conflict
0x29167fcb…2e92
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 0xbf68b5d236…8c0eba
Audit this contract →
← previous block·next block →recent activity