← previous blocknext block →recent activity
Analyzing
Block #100,599,999
32 transactions · 30 stateful · 2026-08-30 23:23:40 UTC
Parallelism
63/100
Blocked
73%
Avg conflicts / tx
2.13
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,599,999 · 32 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w18w416w417w519w420w522w623w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x55590cb2…4785
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0xd5b10148…e637
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity