← previous blocknext block →recent activity
Analyzing
Block #101,934,416
37 transactions · 33 stateful · 2026-09-04 15:19:16 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,934,416 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w110w211w222w323w427w331w432w533w634w735w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0xb409e204…89ac
0x34b655…2a6f
10 touches
10 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
10 touches
10 conflicts
0xba5743c7…21c0
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity