← previous blocknext block →recent activity
Analyzing
Block #101,669,036
55 transactions · 47 stateful · 2026-09-03 17:02:36 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2.38
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #101,669,036 · 55 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w09w115w116w121w223w324w425w526w635w136w737w838w940w1141w1242w943w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0x37e8957a…34e1
0x34b655…2a6f
10 touches
10 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
10 touches
10 conflicts
0x20b1228b…2487
0x34b655…2a6f
10 touches
10 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xa1a01ded…c087
0x34b655…2a6f
10 touches
10 conflicts
0x29a58269…011a
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity