Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f070dda3809759814b9cfa83c3b286d1e450991fa14d43756f27c3fca561d565

Tx prefix hash: 262ab4fc6356eee01cf783338efce0b74a9b2c32d80ecc7d2285d7b16ad1d57c
Tx public key: 096564fb3e9f4a0fa3b217f20f5a33ec59e779c4ccd2049cb6871c829f65bd7d
Timestamp: 1765313628 Timestamp [UCT]: 2025-12-09 20:53:48 Age [y:d:h:m:s]: 00:011:16:18:22
Block: 1430093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8363 RingCT/type: yes/0
Extra: 01096564fb3e9f4a0fa3b217f20f5a33ec59e779c4ccd2049cb6871c829f65bd7d02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21cc988f1cca9b405a2d6bf09b33378ee95e43c91e5d7c2f45137d64663188e4 0.600000000000 1918826 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": 1430103, "vin": [ { "gen": { "height": 1430093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21cc988f1cca9b405a2d6bf09b33378ee95e43c91e5d7c2f45137d64663188e4" } } ], "extra": [ 1, 9, 101, 100, 251, 62, 159, 74, 15, 163, 178, 23, 242, 15, 90, 51, 236, 89, 231, 121, 196, 204, 210, 4, 156, 182, 135, 28, 130, 159, 101, 189, 125, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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