← previous blocknext block →recent activity
Analyzing
Block #100,266,719
18 transactions · 13 stateful · 2026-08-29 19:24:33 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,266,719 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w111w012w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5037e761…ba87
0x34b655…2a6f
4 touches
1 conflict
0xab7f4e6b…8093
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc92109ad…690f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1db5837f…1264
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
1 conflict on slot 0x5037e7618b…a3ba87
Audit this contract →
← previous block·next block →recent activity