← previous blocknext block →recent activity
Analyzing
Block #104,149,029
24 transactions · 23 stateful · 2026-09-12 09:52:42 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,149,029 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w516w617w619w720w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3c2892bf…9a20
0x34b655…2a6f
8 touches
6 conflicts
0x93aa1b2e…8459
0x34b655…2a6f
8 touches
6 conflicts
0x3d8c0e3e…2aad
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
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
21 conflicts on slot 0x705a9a1af8…69db08
Audit this contract →
← previous block·next block →recent activity