← previous blocknext block →recent activity
Analyzing
Block #90,326,653
9 transactions · 8 stateful · 2026-07-25 22:57:47 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,326,653 · 9 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
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66f7c9fa…39a3
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x9a964905…d410
0x34b655…2a6f
4 touches
1 conflict
0xbdc75c16…0d48
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x6254804c…a03b
0x34b655…2a6f
2 touches
0 conflicts
0x6254804c…a03c
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 0x66f7c9fa00…2039a3
Audit this contract →
← previous block·next block →recent activity