← previous blocknext block →recent activity
Analyzing
Block #100,600,435
17 transactions · 12 stateful · 2026-08-30 23:25:52 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,600,435 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x869f8fe9…9d83
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x10f79000…daa5
0x34b655…2a6f
2 touches
0 conflicts
0x1b440234…3c07
0x34b655…2a6f
2 touches
0 conflicts
0x1d26d55a…aacd
0x34b655…2a6f
2 touches
0 conflicts
0x40ea0e78…f58f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x869f8fe964…c09d83
Audit this contract →
← previous block·next block →recent activity