← previous blocknext block →recent activity
Analyzing
Block #90,294,411
15 transactions · 14 stateful · 2026-07-25 20:13:52 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,294,411 · 15 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0649b8e0…c704
0x34b655…2a6f
4 touches
1 conflict
0x189e374d…c093
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0xfaa5c672…5681
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x69c491e3…98d9
0x34b655…2a6f
2 touches
0 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
2 touches
0 conflicts
0xe2d0ed2b…e416
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 0x0649b8e009…10c704
Audit this contract →
← previous block·next block →recent activity