← previous blocknext block →recent activity
Analyzing
Block #100,614,147
24 transactions · 23 stateful · 2026-08-31 00:34:52 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,614,147 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w27w08w19w312w413w514w615w718w119w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfaa9666…2003
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 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 0xdfaa9666ca…322003
Audit this contract →
← previous block·next block →recent activity