Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2678da8d9450d00adf9ce1e991805d361326e1a1d0ca6608181d6793a2372c9b

Tx prefix hash: 04519da86e34ee3998c1c50188f536db81f9faacafdee85e21c97a0e0ebf3bd6
Tx public key: 1cd89af48c95b13d924cbffbe4c75512f20991b4416a0c663942de5386ff95e5
Timestamp: 1715670899 Timestamp [UCT]: 2024-05-14 07:14:59 Age [y:d:h:m:s]: 00:287:03:21:49
Block: 1021671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205205 RingCT/type: yes/0
Extra: 011cd89af48c95b13d924cbffbe4c75512f20991b4416a0c663942de5386ff95e5021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ee8ed6d6c46cf54b00780dbf761edcb944b7f40594b8efa8c3af91c9ae72bb2 0.600000000000 1486056 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": 1021681, "vin": [ { "gen": { "height": 1021671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ee8ed6d6c46cf54b00780dbf761edcb944b7f40594b8efa8c3af91c9ae72bb2" } } ], "extra": [ 1, 28, 216, 154, 244, 140, 149, 177, 61, 146, 76, 191, 251, 228, 199, 85, 18, 242, 9, 145, 180, 65, 106, 12, 102, 57, 66, 222, 83, 134, 255, 149, 229, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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