← previous blocknext block →recent activity
Analyzing
Block #100,612,656
25 transactions · 24 stateful · 2026-08-31 00:27:22 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,612,656 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w08w19w210w312w413w114w517w218w620w122w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xdacb6460…2769
0x34b655…2a6f
8 touches
6 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
8 touches
6 conflicts
0x0f43bfc7…1de5
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity