← previous blocknext block →recent activity
Analyzing
Block #99,972,262
66 transactions · 52 stateful · 2026-08-28 18:40:39 UTC
Parallelism
62/100
Blocked
83%
Avg conflicts / tx
3.88
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #99,972,262 · 66 txs across 25 waves · depth 25
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w914w1016w1119w1039w1146w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x784ce0ea…d14d
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…001a
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…002a
0x1b6862…e19c
22 touches
55 conflicts
0x7322fb4a…635a
0x1b6862…e19c
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
22 touches
55 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity