← previous blocknext block →recent activity
Analyzing
Block #100,587,685
18 transactions · 17 stateful · 2026-08-30 22:21:44 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,587,685 · 18 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
1w02w07w08w19w210w311w414w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5bec32a…b8c3
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0x5ea03500…f0da
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xd5bec32a69…cbb8c3
Audit this contract →
← previous block·next block →recent activity