← previous blocknext block →recent activity
Analyzing
Block #90,637,413
14 transactions · 13 stateful · 2026-07-27 01:12:51 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,637,413 · 14 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
4w05w17w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa840aa62…c5d8
0x34b655…2a6f
6 touches
3 conflicts
0x0342f580…8b21
0x34b655…2a6f
6 touches
3 conflicts
0x3f798539…99c4
0x34b655…2a6f
6 touches
3 conflicts
0x7b0665e8…fbdf
0x34b655…2a6f
4 touches
1 conflict
0xc2a783bf…25e3
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x26d1c221…4d2a
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 0xa840aa62a9…b5c5d8
Audit this contract →
← previous block·next block →recent activity