← previous blocknext block →recent activity
Analyzing
Block #100,864,334
16 transactions · 14 stateful · 2026-08-31 21:33:47 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,864,334 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059e0ac0…0267
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3d041c03…6ba5
0xd32edf…ff58
5 touches
3 conflicts
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0xf1b7e6d1…a6f3
0x34b655…2a6f
3 touches
1 conflict
0x38fa67ab…0ecc
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x059e0ac09d…0f0267
Audit this contract →
← previous block·next block →recent activity