Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e4dd416177d5a0a19c223ffc1fc27f42d8e8e92083edb5d2b85aa42c472ba5

Tx prefix hash: b68adabe6a22b96433b9b85d9a965926d7629a1c6cc09a6c021038d378f1d2df
Tx public key: c209cfde47c32eb6b625f8f098547f7a70026f049122e451d3146910ede3ecf6
Timestamp: 1716058718 Timestamp [UCT]: 2024-05-18 18:58:38 Age [y:d:h:m:s]: 01:173:16:51:11
Block: 1024879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382740 RingCT/type: yes/0
Extra: 01c209cfde47c32eb6b625f8f098547f7a70026f049122e451d3146910ede3ecf602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f25233a458c94c229e34ac326df364e8c76ca6e25c24beded9912313bb3ed91 0.600000000000 1490972 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": 1024889, "vin": [ { "gen": { "height": 1024879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f25233a458c94c229e34ac326df364e8c76ca6e25c24beded9912313bb3ed91" } } ], "extra": [ 1, 194, 9, 207, 222, 71, 195, 46, 182, 182, 37, 248, 240, 152, 84, 127, 122, 112, 2, 111, 4, 145, 34, 228, 81, 211, 20, 105, 16, 237, 227, 236, 246, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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