← previous blocknext block →recent activity
Analyzing
Block #101,681,610
30 transactions · 29 stateful · 2026-09-03 18:05:52 UTC
Parallelism
47/100
Blocked
66%
Avg conflicts / tx
3.37
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #101,681,610 · 30 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w17w08w113w214w215w318w419w520w621w722w824w1025w1126w1227w1328w1429w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x51fc8795…126f
0x34b655…2a6f
24 touches
66 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
20 touches
45 conflicts
0x7dd96c96…7335
0x34b655…2a6f
20 touches
45 conflicts
0xb0e8e2d9…121d
0x34b655…2a6f
8 touches
6 conflicts
0x582cac9c…2571
0x34b655…2a6f
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
8 touches
6 conflicts
0x6dac1990…2656
0x34b655…2a6f
7 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity