Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48dc112b96dff85a732c0e0cf3bdf03e286ad11f61504f99e74481e1eeba5318

Tx prefix hash: cdb1ec40c056da33c0170bbdfd01f69acc12db51228b1f6a417d676c49ddb813
Tx public key: 428cd022a363e7103ec33e52ce5d53eb6236d63136f0d0e61b8b320d99454a2e
Timestamp: 1733869322 Timestamp [UCT]: 2024-12-10 22:22:02 Age [y:d:h:m:s]: 00:102:08:33:14
Block: 1172445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72932 RingCT/type: yes/0
Extra: 01428cd022a363e7103ec33e52ce5d53eb6236d63136f0d0e61b8b320d99454a2e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42dcfb90335de961703a26b3ca6de330fb8a50629b391f5255e1a6d8a38b4bbb 0.600000000000 1658336 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": 1172455, "vin": [ { "gen": { "height": 1172445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42dcfb90335de961703a26b3ca6de330fb8a50629b391f5255e1a6d8a38b4bbb" } } ], "extra": [ 1, 66, 140, 208, 34, 163, 99, 231, 16, 62, 195, 62, 82, 206, 93, 83, 235, 98, 54, 214, 49, 54, 240, 208, 230, 27, 139, 50, 13, 153, 69, 74, 46, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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