Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b636eb66ff4f49375c418ee898abd93cecb858b76ca93c23b72aec1b0679d6bf

Tx prefix hash: ad1996c3db98aa0cd03f328f7f4f0685789d3026e5724ff4ccdecaf55ab2d946
Tx public key: 0d667c1abd79a9223ff8858c064b7c394b5c7ab0e5b0bd6a68132f0d5e419852
Timestamp: 1705608994 Timestamp [UCT]: 2024-01-18 20:16:34 Age [y:d:h:m:s]: 01:076:04:41:12
Block: 938228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315554 RingCT/type: yes/0
Extra: 010d667c1abd79a9223ff8858c064b7c394b5c7ab0e5b0bd6a68132f0d5e4198520211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3f2118f7e6cfbcf290522127ee3199e360acde2d8c25335b9e65527c6415fd 0.600000000000 1396298 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": 938238, "vin": [ { "gen": { "height": 938228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3f2118f7e6cfbcf290522127ee3199e360acde2d8c25335b9e65527c6415fd" } } ], "extra": [ 1, 13, 102, 124, 26, 189, 121, 169, 34, 63, 248, 133, 140, 6, 75, 124, 57, 75, 92, 122, 176, 229, 176, 189, 106, 104, 19, 47, 13, 94, 65, 152, 82, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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