← previous blocknext block →recent activity
Analyzing
Block #100,023,060
19 transactions · 19 stateful · 2026-08-28 22:56:28 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,023,060 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w08w09w111w212w314w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30b0b461…88ae
0x34b655…2a6f
6 touches
3 conflicts
0xf98c943e…7c44
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
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 0x30b0b46142…6788ae
Audit this contract →
← previous block·next block →recent activity