← previous blocknext block →recent activity
Analyzing
Block #90,242,669
7 transactions · 3 stateful · 2026-07-25 15:52:13 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,242,669 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc6989370…e327
0x34b655…2a6f
4 touches
1 conflict
0xf2ba301a…ca6d
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x07905888…65ef
0x34b655…2a6f
2 touches
0 conflicts
0x172b0de5…980b
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 0xa6b48d6e52…7c0705
Audit this contract →
← previous block·next block →recent activity