← previous blocknext block →recent activity
Analyzing
Block #100,565,482
17 transactions · 17 stateful · 2026-08-30 20:30:03 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,565,482 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w210w111w012w214w315w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fba5536…cc75
0x34b655…2a6f
8 touches
6 conflicts
0x33000c0a…82c3
0x34b655…2a6f
6 touches
3 conflicts
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x03f9cc30…b46b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
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 0x6fba5536e5…36cc75
Audit this contract →
← previous block·next block →recent activity