Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bac06f46da2f9937af8bb7996673e7acfb3584a560c29302af67afae1b576be3

Tx prefix hash: d1fe17a3db5f74cb07d024332f3741f44b933f52ffc5dfbf3a72e5ebe3ebdf80
Tx public key: 0c533627e9c14dbec583cff33dcc1ce86c0d6587252f0a90f248e7e43fe0b612
Timestamp: 1720909832 Timestamp [UCT]: 2024-07-13 22:30:32 Age [y:d:h:m:s]: 00:133:17:19:04
Block: 1065106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95688 RingCT/type: yes/0
Extra: 010c533627e9c14dbec583cff33dcc1ce86c0d6587252f0a90f248e7e43fe0b61202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129d3753e21a7ed4c650970337030ce5d17d7d936b501603dd6064e02b1b91c3 0.600000000000 1535649 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": 1065116, "vin": [ { "gen": { "height": 1065106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129d3753e21a7ed4c650970337030ce5d17d7d936b501603dd6064e02b1b91c3" } } ], "extra": [ 1, 12, 83, 54, 39, 233, 193, 77, 190, 197, 131, 207, 243, 61, 204, 28, 232, 108, 13, 101, 135, 37, 47, 10, 144, 242, 72, 231, 228, 63, 224, 182, 18, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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