← previous blocknext block →recent activity
Analyzing
Block #104,202,947
24 transactions · 21 stateful · 2026-09-12 14:26:26 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
2.58
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #104,202,947 · 24 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w411w514w616w717w818w919w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xcd1306ad…f1b8
0x34b655…2a6f
12 touches
15 conflicts
0x485c6978…f98f
0x34b655…2a6f
10 touches
10 conflicts
0x9ece6df2…b665
0x34b655…2a6f
10 touches
10 conflicts
0xdde0659e…2dbc
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity