← previous blocknext block →recent activity
Analyzing
Block #100,920,467
24 transactions · 20 stateful · 2026-09-01 02:16:08 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
1.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,920,467 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w312w413w516w621w722w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
12 touches
15 conflicts
0xfd0635f7…0716
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xeff238b4…7296
0x34b655…2a6f
6 touches
3 conflicts
0x23529e13…6f25
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x53f7214d…8ec6
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 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity