← previous blocknext block →recent activity
Analyzing
Block #102,277,428
22 transactions · 19 stateful · 2026-09-05 20:18:01 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,277,428 · 22 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
1w02w14w05w17w09w010w112w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x2509e442…3427
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0005a008…264a
0x34b655…2a6f
4 touches
1 conflict
0x256918f1…c4d0
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity