← previous blocknext block →recent activity
Analyzing
Block #100,046,770
14 transactions · 14 stateful · 2026-08-29 00:55:49 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,046,770 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb240b520…a88a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x4dbf4de0…2dc2
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x34acbcd7…322a
0x34b655…2a6f
6 touches
3 conflicts
0xb35e0bd9…84c1
0x34b655…2a6f
4 touches
1 conflict
0xce485734…7ac7
0x34b655…2a6f
4 touches
1 conflict
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 0xb240b520db…67a88a
Audit this contract →
← previous block·next block →recent activity