← previous blocknext block →recent activity
Analyzing
Block #101,924,433
20 transactions · 20 stateful · 2026-09-04 14:28:35 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,924,433 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w08w09w112w113w115w216w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0x66d0c4a4…add3
0x34b655…2a6f
6 touches
3 conflicts
0x7a9ed1db…a9cf
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0xaef54d0e…bc8e
0x34b655…2a6f
6 touches
3 conflicts
0xc52785b9…08f8
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity