← previous blocknext block →recent activity
Analyzing
Block #100,085,122
19 transactions · 18 stateful · 2026-08-29 04:08:53 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.16
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,085,122 · 19 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
1w02w13w24w05w19w010w111w112w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xbd590df7…9891
0x34b655…2a6f
16 touches
28 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
14 touches
21 conflicts
0x659933ab…e189
0x34b655…2a6f
8 touches
6 conflicts
0x23ef1567…8f31
0x34b655…2a6f
8 touches
6 conflicts
0x9771c5e6…5d7b
0x34b655…2a6f
7 touches
6 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity