← previous blocknext block →recent activity
Analyzing
Block #100,706,176
22 transactions · 20 stateful · 2026-08-31 08:17:46 UTC
Parallelism
73/100
Blocked
60%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,706,176 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w38w49w211w312w413w014w116w518w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0ded688…b825
0x34b655…2a6f
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xab2a87f1…eafc
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xc0ded68877…76b825
Audit this contract →
← previous block·next block →recent activity