Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcedfd8df746e8f86044e88b7f521c138178b4ff6fe95fcd14a8e9b687934e3a

Tx prefix hash: 444caf30d39cfd4ef476f68b439df44dda74269e7b5464aaff4aff6ee27e8ba2
Tx public key: 568bab96861aa5834c5b139aa1812cfd0853ddcd1ffc7f96bab59ed9b1057a5f
Timestamp: 1588265853 Timestamp [UCT]: 2020-04-30 16:57:33 Age [y:d:h:m:s]: 04:200:12:00:52
Block: 97471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1057279 RingCT/type: yes/0
Extra: 01568bab96861aa5834c5b139aa1812cfd0853ddcd1ffc7f96bab59ed9b1057a5f0211000000076fa03929000000000000000000

1 output(s) for total of 291.768821010000 dcy

stealth address amount amount idx
00: cf6eeaa4eb3f1a7e6d03a681781573cad5ec03443c31711d3fbf8e98a43657c0 291.768821010000 172502 of 0

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": 97481, "vin": [ { "gen": { "height": 97471 } } ], "vout": [ { "amount": 291768821010, "target": { "key": "cf6eeaa4eb3f1a7e6d03a681781573cad5ec03443c31711d3fbf8e98a43657c0" } } ], "extra": [ 1, 86, 139, 171, 150, 134, 26, 165, 131, 76, 91, 19, 154, 161, 129, 44, 253, 8, 83, 221, 205, 31, 252, 127, 150, 186, 181, 158, 217, 177, 5, 122, 95, 2, 17, 0, 0, 0, 7, 111, 160, 57, 41, 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