← previous blocknext block →recent activity
Analyzing
Block #90,113,666
9 transactions · 8 stateful · 2026-07-25 05:01:42 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,113,666 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d05e294…dfe5
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xd9a117fc…2349
0x34b655…2a6f
4 touches
1 conflict
0xe142614c…cd9e
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6628
0x34b655…2a6f
2 touches
0 conflicts
0x0892061a…f40b
0x34b655…2a6f
2 touches
0 conflicts
0x08b1b3da…194e
0x34b655…2a6f
2 touches
0 conflicts
0x0af5f342…d3fc
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 0x0d05e2942f…b8dfe5
Audit this contract →
← previous block·next block →recent activity