← previous blocknext block →recent activity
Analyzing
Block #101,022,318
46 transactions · 43 stateful · 2026-09-01 10:48:33 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
2.13
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #101,022,318 · 46 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w08w19w010w011w112w216w119w120w221w322w423w524w633w335w336w538w140w842w1043w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x40f0cbff…df7c
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity