← previous blocknext block →recent activity
Analyzing
Block #90,026,410
15 transactions · 14 stateful · 2026-07-24 21:39:18 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,026,410 · 15 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
6w07w18w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67bfbc55…7b2f
0x34b655…2a6f
4 touches
1 conflict
0xaf151f7f…3fe4
0x34b655…2a6f
4 touches
1 conflict
0xb27ed09c…19bd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe999cbf5…d18a
0x34b655…2a6f
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x67bfbc5533…247b2f
Audit this contract →
← previous block·next block →recent activity