← previous blocknext block →recent activity
Analyzing
Block #102,404,384
14 transactions · 13 stateful · 2026-09-06 07:01:12 UTC
Parallelism
71/100
Blocked
62%
Avg conflicts / tx
1.14
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,404,384 · 14 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
1w02w13w24w39w110w211w312w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a653a3f…f811
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6c6f37ba…c207
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 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
6 conflicts on slot 0x6a653a3f71…f5f811
Audit this contract →
← previous block·next block →recent activity