← previous blocknext block →recent activity
Analyzing
Block #90,638,614
10 transactions · 9 stateful · 2026-07-27 01:18:53 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,638,614 · 10 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
3w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd442ac37…1609
0x34b655…2a6f
4 touches
1 conflict
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0dc85d02…57bb
0x34b655…2a6f
2 touches
0 conflicts
0x0e526172…9fc4
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 0xd442ac3711…dd1609
Audit this contract →
← previous block·next block →recent activity