← previous blocknext block →recent activity
Analyzing
Block #100,739,909
46 transactions · 37 stateful · 2026-08-31 11:07:28 UTC
Parallelism
85/100
Blocked
54%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,739,909 · 46 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
1w02w13w24w37w48w59w611w038w642w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x06e40499…165e
0x34ae4d…3fc5
10 touches
10 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 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: 0xf5b5f7f8…a36d70
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity