← previous blocknext block →recent activity
Analyzing
Block #100,236,496
16 transactions · 13 stateful · 2026-08-29 16:51:04 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,236,496 · 16 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
1w04w15w28w39w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe709bf68…3f97
0x34b655…2a6f
12 touches
15 conflicts
0x29cd05f5…390c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
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
15 conflicts on slot 0xe709bf68c0…963f97
Audit this contract →
← previous block·next block →recent activity