Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdcc47034d5cd47b21654200f5e61a095c4e8a61a60c3df2c0b164c98d7e9fce

Tx prefix hash: 0d257ac52131cd78ef62af7c2febaa646009e9451a3b199dffde08f8a31baa0a
Tx public key: 8fd6598f7feda60f59d474dda1f9d0f02a4d388a71542d019265dfa1cd7fc206
Timestamp: 1759872959 Timestamp [UCT]: 2025-10-07 21:35:59 Age [y:d:h:m:s]: 00:086:21:12:50
Block: 1384998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62221 RingCT/type: yes/0
Extra: 018fd6598f7feda60f59d474dda1f9d0f02a4d388a71542d019265dfa1cd7fc206021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0b860dda0d4710b4b2c763f50af479cba182a398531e53d600bd175a81b987 0.600000000000 1873155 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": 1385008, "vin": [ { "gen": { "height": 1384998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0b860dda0d4710b4b2c763f50af479cba182a398531e53d600bd175a81b987" } } ], "extra": [ 1, 143, 214, 89, 143, 127, 237, 166, 15, 89, 212, 116, 221, 161, 249, 208, 240, 42, 77, 56, 138, 113, 84, 45, 1, 146, 101, 223, 161, 205, 127, 194, 6, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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