← previous blocknext block →recent activity
Analyzing
Block #90,459,493
9 transactions · 8 stateful · 2026-07-26 10:17:47 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,459,493 · 9 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
1w02w14w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3f008b3…b7c9
0x34b655…2a6f
4 touches
1 conflict
0xcd9f71fa…2ec5
0x34b655…2a6f
4 touches
1 conflict
0xd708bac6…2e5d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0x20fbcaee…bb79
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x36a76bd2…1fb0
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 0xb3f008b3b9…6ab7c9
Audit this contract →
← previous block·next block →recent activity