← previous blocknext block →recent activity
Analyzing
Block #100,439,747
21 transactions · 19 stateful · 2026-08-30 09:57:26 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,439,747 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w18w29w310w111w012w117w219w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0f57943…818d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c2
0x1b6862…e19c
8 touches
6 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
6 conflicts on slot 0xe0f5794396…a3818d
Audit this contract →
← previous block·next block →recent activity