← previous blocknext block →recent activity
Analyzing
Block #89,405,190
16 transactions · 15 stateful · 2026-07-22 10:34:43 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,405,190 · 16 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
1w02w16w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f87cdf…e5b6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2bac71c3…3296
0x34b655…2a6f
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x4574ff69…ccf7
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x9212c1f0…3103
0x065c9d…c394
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 0x67f87cdf50…cde5b6
Audit this contract →
← previous block·next block →recent activity