← previous blocknext block →recent activity
Analyzing
Block #90,040,761
16 transactions · 15 stateful · 2026-07-24 22:51:37 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,040,761 · 16 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
1w02w17w08w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaca60768…7272
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe4eafc97…cbbf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x204ccae2…8dc1
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
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
1 conflict on slot 0xaca6076827…fa7272
Audit this contract →
← previous block·next block →recent activity