Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4cbdabddee61e3797752f5cc708b2ee008b2ded29a2397475ebe47ca924bbb9c

Tx prefix hash: f5b69c8db10d85b89b25676d63424f9512dc6508c905b5cc600ea06366ee123b
Tx public key: 5d49a52062cdd4865fdc4e295db11a8cfad8e961a891ab6a3d2ebc2ae6a47ce5
Timestamp: 1760925895 Timestamp [UCT]: 2025-10-20 02:04:55 Age [y:d:h:m:s]: 00:037:13:05:33
Block: 1393752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26864 RingCT/type: yes/0
Extra: 015d49a52062cdd4865fdc4e295db11a8cfad8e961a891ab6a3d2ebc2ae6a47ce5021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64029164ce88b65bfb17036122f03bafcedcd5d8516d8cdebfddfe0b3e860e6 0.600000000000 1882019 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1393762, "vin": [ { "gen": { "height": 1393752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64029164ce88b65bfb17036122f03bafcedcd5d8516d8cdebfddfe0b3e860e6" } } ], "extra": [ 1, 93, 73, 165, 32, 98, 205, 212, 134, 95, 220, 78, 41, 93, 177, 26, 140, 250, 216, 233, 97, 168, 145, 171, 106, 61, 46, 188, 42, 230, 164, 124, 229, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8