Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efe25958c91c97fdb042860f1b8523936a7d4f7aaeced9e291b55dfcc68aa7ab

Tx prefix hash: 8f5cd03c780f2a5d3e7d0a63ff00fdf2864d20b0c494594649aa7933d5be7db7
Tx public key: 981dbf1ea1cc1d87280a479687a3682c592b8cf26e08e6bdec1267b167fe83ff
Timestamp: 1708269208 Timestamp [UCT]: 2024-02-18 15:13:28 Age [y:d:h:m:s]: 00:344:02:02:25
Block: 960302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246074 RingCT/type: yes/0
Extra: 01981dbf1ea1cc1d87280a479687a3682c592b8cf26e08e6bdec1267b167fe83ff0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f65db9482b0aa1eb46ced5ea283c350a7badeab45af5ee6bbf56ce1093c4755 0.600000000000 1419865 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": 960312, "vin": [ { "gen": { "height": 960302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f65db9482b0aa1eb46ced5ea283c350a7badeab45af5ee6bbf56ce1093c4755" } } ], "extra": [ 1, 152, 29, 191, 30, 161, 204, 29, 135, 40, 10, 71, 150, 135, 163, 104, 44, 89, 43, 140, 242, 110, 8, 230, 189, 236, 18, 103, 177, 103, 254, 131, 255, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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