Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ade17377bd7099e6bdcbbc7c622f818f5de8be71ff1f0c82ae08782d9ca5189

Tx prefix hash: 0d4f740fb5e5b822b5667d71d6c9aa9139d1114588e236c0d61337d427d73455
Tx public key: 8b9818a29da1ece56af65bc7892aec6c957a72913b820262ccddf6c663d8ab65
Timestamp: 1730459143 Timestamp [UCT]: 2024-11-01 11:05:43 Age [y:d:h:m:s]: 00:082:12:48:03
Block: 1144181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59016 RingCT/type: yes/0
Extra: 018b9818a29da1ece56af65bc7892aec6c957a72913b820262ccddf6c663d8ab650211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd7a5d3113e0d66e69445bdc865a1b224b15de00150355479ab14e270a43ecb3 0.600000000000 1628308 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": 1144191, "vin": [ { "gen": { "height": 1144181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd7a5d3113e0d66e69445bdc865a1b224b15de00150355479ab14e270a43ecb3" } } ], "extra": [ 1, 139, 152, 24, 162, 157, 161, 236, 229, 106, 246, 91, 199, 137, 42, 236, 108, 149, 122, 114, 145, 59, 130, 2, 98, 204, 221, 246, 198, 99, 216, 171, 101, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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