← previous blocknext block →recent activity
Analyzing
Block #90,029,492
14 transactions · 12 stateful · 2026-07-24 21:54:50 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,029,492 · 14 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
1w02w17w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x4b482505…30c1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x6230d909…d51b
0xa6afd3…d132
3 touches
1 conflict
0x496f98b6…66b5
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x10379e8db9…2b3675
Audit this contract →
← previous block·next block →recent activity