Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 818e7189df757c21e1ce758402750b4df6c39d753bb944e3ebcdb9e1f530d176

Tx prefix hash: b104d4f2a9983b0e138e9048cdaae2abf1d2294145cbc425dbf2dcb28851d841
Tx public key: 97d82c4346accb4fd3e5e21b7fd98995e78319d91025572732f5793cadb44779
Timestamp: 1717349648 Timestamp [UCT]: 2024-06-02 17:34:08 Age [y:d:h:m:s]: 00:364:16:29:19
Block: 1035591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260677 RingCT/type: yes/0
Extra: 0197d82c4346accb4fd3e5e21b7fd98995e78319d91025572732f5793cadb447790211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da733d2c721aaa6c7e27659ba1ce9860f4fba24d5dc47b4364ac90ea1aa6d489 0.600000000000 1504112 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": 1035601, "vin": [ { "gen": { "height": 1035591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da733d2c721aaa6c7e27659ba1ce9860f4fba24d5dc47b4364ac90ea1aa6d489" } } ], "extra": [ 1, 151, 216, 44, 67, 70, 172, 203, 79, 211, 229, 226, 27, 127, 217, 137, 149, 231, 131, 25, 217, 16, 37, 87, 39, 50, 245, 121, 60, 173, 180, 71, 121, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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