← previous blocknext block →recent activity
Analyzing
Block #101,656,983
36 transactions · 28 stateful · 2026-09-03 16:01:58 UTC
Parallelism
69/100
Blocked
75%
Avg conflicts / tx
2.47
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,656,983 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w29w310w411w512w613w714w815w916w1018w121w222w323w427w528w132w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb654bd89…a83b
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x2eca27fa…dba4
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: 0xf5b5f7f8…a36d70
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity