← previous blocknext block →recent activity
Analyzing
Block #90,430,430
10 transactions · 9 stateful · 2026-07-26 07:50:15 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,430,430 · 10 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
4w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xcf5e16e2…f2a7
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xdab87f9b…3a80
0x34b655…2a6f
4 touches
1 conflict
0x45b57036…844b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd86f1527…3226
0x34b655…2a6f
4 touches
1 conflict
0xcbb82c6b…c5ea
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity