← previous blocknext block →recent activity
Analyzing
Block #100,031,747
25 transactions · 19 stateful · 2026-08-28 23:40:12 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,031,747 · 25 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
9w011w115w016w117w119w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd5a06f0…6ccd
0x34b655…2a6f
6 touches
3 conflicts
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xa18d515f…b4de
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xdd5a06f0a6…9f6ccd
Audit this contract →
← previous block·next block →recent activity