← previous blocknext block →recent activity
Analyzing
Block #100,267,000
16 transactions · 16 stateful · 2026-08-29 19:26:00 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,267,000 · 16 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
1w03w04w17w18w210w312w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2c001e45…d749
0x34b655…2a6f
8 touches
6 conflicts
0xc7b7b345…1d04
0x34b655…2a6f
8 touches
6 conflicts
0x831f75b4…945d
0x34b655…2a6f
4 touches
1 conflict
0x8aa1715e…af62
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity