Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05962caa2514aacfef2f59225f4aef44aef5bd5a8d9b9e7a802da5838585bbd8

Tx prefix hash: a5c9a2d046af30f502eb60e9645def81a05bfb158feb1fb86e8eb376658479d7
Tx public key: 1f1e00bbdc4c3e076d215cad2fc9f5419dd9d72b55bb34eba44244278422063d
Timestamp: 1730113974 Timestamp [UCT]: 2024-10-28 11:12:54 Age [y:d:h:m:s]: 00:207:20:27:56
Block: 1141333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148422 RingCT/type: yes/0
Extra: 011f1e00bbdc4c3e076d215cad2fc9f5419dd9d72b55bb34eba44244278422063d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cde627aaa530df144448c3fa5178b3e2086bc002b5c4f0fd07b553ff4ec3652 0.600000000000 1625140 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": 1141343, "vin": [ { "gen": { "height": 1141333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cde627aaa530df144448c3fa5178b3e2086bc002b5c4f0fd07b553ff4ec3652" } } ], "extra": [ 1, 31, 30, 0, 187, 220, 76, 62, 7, 109, 33, 92, 173, 47, 201, 245, 65, 157, 217, 215, 43, 85, 187, 52, 235, 164, 66, 68, 39, 132, 34, 6, 61, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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