← previous blocknext block →recent activity
Analyzing
Block #102,173,214
19 transactions · 15 stateful · 2026-09-05 11:30:00 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,173,214 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w210w311w413w514w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd5c03fa…922b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1a2055c7…9054
0x34b655…2a6f
10 touches
10 conflicts
0x70a7b5d6…fe0e
0x34b655…2a6f
10 touches
10 conflicts
0x8cba9eaf…6f99
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xcc8b6d32…6601
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
15 conflicts on slot 0xbd5c03faea…11922b
Audit this contract →
← previous block·next block →recent activity