← previous blocknext block →recent activity
Analyzing
Block #100,604,162
76 transactions · 45 stateful · 2026-08-30 23:44:38 UTC
Parallelism
71/100
Blocked
76%
Avg conflicts / tx
2.53
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #100,604,162 · 76 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w08w09w111w213w316w135w341w443w644w745w846w947w1048w1152w254w355w457w458w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x4062abac…1e0e
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001e
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002e
0x1b6862…e19c
20 touches
45 conflicts
0x98067f20…59e9
0x1b6862…e19c
20 touches
45 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity