← previous blocknext block →recent activity
Analyzing
Block #99,957,989
34 transactions · 32 stateful · 2026-08-28 17:28:46 UTC
Parallelism
56/100
Blocked
69%
Avg conflicts / tx
3.38
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #99,957,989 · 34 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w08w011w212w113w215w016w117w218w319w420w521w622w723w824w925w1026w1127w1228w1329w1431w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51ee0faa…d7af
0x912009…bb53
30 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
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: 0x9120090c…dfbb53
105 conflicts on slot 0x51ee0faaba…e5d7af
Audit this contract →
← previous block·next block →recent activity