← previous blocknext block →recent activity
Analyzing
Block #100,626,753
19 transactions · 18 stateful · 2026-08-31 01:38:16 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,626,753 · 19 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
1w02w13w25w18w010w011w112w313w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x0ff4d33f…6dde
0x34b655…2a6f
6 touches
3 conflicts
0xb240b520…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x7a54ee46…4676
0x34b655…2a6f
6 touches
3 conflicts
0xfac61869…a562
0x1b6862…e19c
6 touches
3 conflicts
0xd69b4a42…3ab4
0xd32edf…ff58
5 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity