Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7e4673e813f5b7b5107b22414fdc8cf654756818e0d6aea66817a0f827a81f3

Tx prefix hash: a668157a9043e6f8eb0b82abbc29bde4441c2b174c9fcdd986f2701db3f42333
Tx public key: c551c3900a306782dc15554608884e29a59adf5777fdc5513c2b5a0cd8afe80c
Timestamp: 1720610207 Timestamp [UCT]: 2024-07-10 11:16:47 Age [y:d:h:m:s]: 00:196:12:53:12
Block: 1062623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140575 RingCT/type: yes/0
Extra: 01c551c3900a306782dc15554608884e29a59adf5777fdc5513c2b5a0cd8afe80c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f43b940f3ec35add7bd9e71380c965839c17f681209c34088bcaa1fddc887b23 0.600000000000 1533128 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": 1062633, "vin": [ { "gen": { "height": 1062623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f43b940f3ec35add7bd9e71380c965839c17f681209c34088bcaa1fddc887b23" } } ], "extra": [ 1, 197, 81, 195, 144, 10, 48, 103, 130, 220, 21, 85, 70, 8, 136, 78, 41, 165, 154, 223, 87, 119, 253, 197, 81, 60, 43, 90, 12, 216, 175, 232, 12, 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