Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4beba11522482bd714247c7468bdd8d5d9b36576bd404f3b59ca4cc435d27aa

Tx prefix hash: 671772e8596d05d2c0a119ba371f36ff75d5f654552fbaf83b3fd5df56c342e7
Tx public key: c21d18557249657a9d8d8236a6a15e4ce726a90c5e39f7cdd0b8cfc9f7aa883e
Timestamp: 1713644999 Timestamp [UCT]: 2024-04-20 20:29:59 Age [y:d:h:m:s]: 01:058:17:41:01
Block: 1004866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302830 RingCT/type: yes/0
Extra: 01c21d18557249657a9d8d8236a6a15e4ce726a90c5e39f7cdd0b8cfc9f7aa883e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc49fc16614f2949bb0a3fa44ce4973fcd6a153f0c581e7c68f5edaa79ddfc1b 0.600000000000 1465440 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": 1004876, "vin": [ { "gen": { "height": 1004866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc49fc16614f2949bb0a3fa44ce4973fcd6a153f0c581e7c68f5edaa79ddfc1b" } } ], "extra": [ 1, 194, 29, 24, 85, 114, 73, 101, 122, 157, 141, 130, 54, 166, 161, 94, 76, 231, 38, 169, 12, 94, 57, 247, 205, 208, 184, 207, 201, 247, 170, 136, 62, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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