← previous blocknext block →recent activity
Analyzing
Block #100,734,576
29 transactions · 25 stateful · 2026-08-31 10:40:39 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,734,576 · 29 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
1w02w13w26w08w19w113w014w115w218w323w424w425w128w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8311570f…5321
0x34b655…2a6f
8 touches
6 conflicts
0x89ac61bf…9443
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x714be73e…a11e
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 0x8311570feb…ae5321
Audit this contract →
← previous block·next block →recent activity