Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae74b36a3da20c6708ff0d429f2be7f156d614ff8c6b7cc4ab96827e264d793

Tx prefix hash: 051bcf6a6153b91ac835928ffef56392c0ca5c9b83362ea542b88c59b0e95fcb
Tx public key: 9a193a53cd83924e663d93d40db615ca094df6e856fc13c24ebdfdd219919848
Timestamp: 1712201134 Timestamp [UCT]: 2024-04-04 03:25:34 Age [y:d:h:m:s]: 00:280:01:34:58
Block: 992864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200503 RingCT/type: yes/0
Extra: 019a193a53cd83924e663d93d40db615ca094df6e856fc13c24ebdfdd21991984802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 306d4ffd2ca161a0401d1b5a29bf47cbbe7527159a757697bffb77377afec5f6 0.600000000000 1453240 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": 992874, "vin": [ { "gen": { "height": 992864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "306d4ffd2ca161a0401d1b5a29bf47cbbe7527159a757697bffb77377afec5f6" } } ], "extra": [ 1, 154, 25, 58, 83, 205, 131, 146, 78, 102, 61, 147, 212, 13, 182, 21, 202, 9, 77, 246, 232, 86, 252, 19, 194, 78, 189, 253, 210, 25, 145, 152, 72, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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