← previous blocknext block →recent activity
Analyzing
Block #100,147,003
16 transactions · 16 stateful · 2026-08-29 09:20:35 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,147,003 · 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
1w02w15w06w07w18w210w211w312w413w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb584ff4d…8750
0x34b655…2a6f
8 touches
6 conflicts
0xf64f1021…e81b
0x34b655…2a6f
8 touches
6 conflicts
0xf98c943e…7c44
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
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 0xb584ff4d00…7d8750
Audit this contract →
← previous block·next block →recent activity