← previous blocknext block →recent activity
Analyzing
Block #100,631,738
21 transactions · 20 stateful · 2026-08-31 02:03:21 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,631,738 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w211w112w213w314w316w317w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c61506…343f
0x34b655…2a6f
8 touches
6 conflicts
0x9d3ba38e…2371
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x6a0638a3…fc78
0x851145…3f07
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc545fdad…74de
0x851145…3f07
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 0x50c615063f…63343f
Audit this contract →
← previous block·next block →recent activity