← previous blocknext block →recent activity
Analyzing
Block #83,900,927
22 transactions · 20 stateful · 2026-06-26 21:54:05 UTC
Parallelism
73/100
Blocked
60%
Avg conflicts / tx
1.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,900,927 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w410w011w112w213w314w415w517w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 conflicts
0x8726ff39…3be8
0x34b655…2a6f
10 touches
10 conflicts
0xe2e45419…f17b
0x34b655…2a6f
10 touches
10 conflicts
0x5df6102c…6494
0xa6afd3…d132
10 touches
10 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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity