Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc470de0ccf95b3c6efca6d5bedf494640ce0e065b71d969e69d1ff0b1bbfd4

Tx prefix hash: 1145f9bf7871dec393e17fac20fe6657d393ef099be2d4d40b90dd17f6643eb8
Tx public key: ae9f22a9c092edd5584ff502dcf9cf02887f8f7aca0b1ef90a8da9ce7a49b9fd
Timestamp: 1707244407 Timestamp [UCT]: 2024-02-06 18:33:27 Age [y:d:h:m:s]: 01:285:13:57:56
Block: 951793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462897 RingCT/type: yes/0
Extra: 01ae9f22a9c092edd5584ff502dcf9cf02887f8f7aca0b1ef90a8da9ce7a49b9fd02110000000f10a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6119e408d1a7976b9983f93a2997727fc28e5373ea188cfa6d772061290bfbb9 0.600000000000 1410617 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": 951803, "vin": [ { "gen": { "height": 951793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6119e408d1a7976b9983f93a2997727fc28e5373ea188cfa6d772061290bfbb9" } } ], "extra": [ 1, 174, 159, 34, 169, 192, 146, 237, 213, 88, 79, 245, 2, 220, 249, 207, 2, 136, 127, 143, 122, 202, 11, 30, 249, 10, 141, 169, 206, 122, 73, 185, 253, 2, 17, 0, 0, 0, 15, 16, 161, 116, 143, 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