← previous blocknext block →recent activity
Analyzing
Block #102,247,443
68 transactions · 68 stateful · 2026-09-05 17:46:03 UTC
Parallelism
94/100
Blocked
12%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,247,443 · 68 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
1w02w13w24w06w010w011w112w261w162w264w367w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f1835a9…a001
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
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 0x7f1835a939…eda001
Audit this contract →
← previous block·next block →recent activity