← previous blocknext block →recent activity
Analyzing
Block #100,155,932
14 transactions · 12 stateful · 2026-08-29 10:05:32 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,155,932 · 14 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
3w04w08w19w210w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x10a5a231…be40
0x34b655…2a6f
8 touches
6 conflicts
0xb19e8c79…7c1b
0x34b655…2a6f
7 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0x61e2c349…73aa
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity