← previous blocknext block →recent activity
Analyzing
Block #104,148,976
23 transactions · 23 stateful · 2026-09-12 09:52:26 UTC
Parallelism
57/100
Blocked
61%
Avg conflicts / tx
2.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,148,976 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w512w613w514w615w716w817w722w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf1352320…c9c3
0x34b655…2a6f
12 touches
15 conflicts
0x7d91b3f5…3838
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
8 touches
6 conflicts
0xc9149f17…e761
0x34b655…2a6f
6 touches
3 conflicts
0x3c34003c…a1f0
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
28 conflicts on slot 0x705a9a1af8…69db08
Audit this contract →
← previous block·next block →recent activity