← previous blocknext block →recent activity
Analyzing
Block #100,747,900
16 transactions · 16 stateful · 2026-08-31 11:47:40 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,747,900 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xec2204ac…0b8c
0x851145…3f07
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x39977254…07b1
0x34ae4d…3fc5
2 touches
0 conflicts
0x3a3e7727…36c5
0x34ae4d…3fc5
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: 0x01bff417…bc1071
10 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity