← previous blocknext block →recent activity
Analyzing
Block #88,090,514
16 transactions · 13 stateful · 2026-07-16 08:01:19 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,090,514 · 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
1w02w14w05w18w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb54bf9fe…be64
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x676baad1…1c45
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0xb54bf9fe1a…60be64
Audit this contract →
← previous block·next block →recent activity