← previous blocknext block →recent activity
Analyzing
Block #100,234,441
21 transactions · 20 stateful · 2026-08-29 16:40:44 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
1.29
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,234,441 · 21 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
1w02w04w05w16w17w08w09w110w211w313w414w516w118w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d17ba18…e2f1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
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
6 conflicts on slot 0x1d17ba18f4…64e2f1
Audit this contract →
← previous block·next block →recent activity