← previous blocknext block →recent activity
Analyzing
Block #100,063,787
18 transactions · 17 stateful · 2026-08-29 02:21:28 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,063,787 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w210w211w312w413w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
12 touches
15 conflicts
0xf95c3143…ac6d
0x34b655…2a6f
12 touches
15 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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
15 conflicts on slot 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity