Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78720136f2a995f87e98c8f49be61c7e3eabd8dc5fc71224bc665f5086ba90be

Tx prefix hash: a1d452b2f8f8ab8e017b1818476064409ee5d54c5f9cf9023d154034a68abc96
Tx public key: 9aff23e693d4b4948c236ea30fff945dca674129bc582f0d70563011496ee78e
Timestamp: 1729374374 Timestamp [UCT]: 2024-10-19 21:46:14 Age [y:d:h:m:s]: 00:169:06:47:04
Block: 1135277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120744 RingCT/type: yes/0
Extra: 019aff23e693d4b4948c236ea30fff945dca674129bc582f0d70563011496ee78e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cc4cb19bf9087b0e72eefad32abb5a1ca34e47015370dc3f7f7ed9fe443e7e5 0.600000000000 1618610 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": 1135287, "vin": [ { "gen": { "height": 1135277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cc4cb19bf9087b0e72eefad32abb5a1ca34e47015370dc3f7f7ed9fe443e7e5" } } ], "extra": [ 1, 154, 255, 35, 230, 147, 212, 180, 148, 140, 35, 110, 163, 15, 255, 148, 93, 202, 103, 65, 41, 188, 88, 47, 13, 112, 86, 48, 17, 73, 110, 231, 142, 2, 17, 0, 0, 0, 2, 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