Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997fea3fa9c5083ce1223026663d6645f1c6e083a3bf74b93f24b954a84d433b

Tx prefix hash: 995650497e6796beac08b77dbfb5b616e2bd7ed163a581b2f74e51076ef0dc2b
Tx public key: e842f9c80829969ade35f9af1b14416695091aea074d01bd869db1d4037a85ba
Timestamp: 1618112473 Timestamp [UCT]: 2021-04-11 03:41:13 Age [y:d:h:m:s]: 03:233:12:11:34
Block: 237261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 927106 RingCT/type: yes/0
Extra: 01e842f9c80829969ade35f9af1b14416695091aea074d01bd869db1d4037a85ba021100000002a1bbccc7000000000000000000

1 output(s) for total of 100.430103880000 dcy

stealth address amount amount idx
00: 3a92ece12acd33e612d70d7e2c7fe6632e68cf5be32b9ed75fb03996d082f6b3 100.430103880000 493699 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": 237271, "vin": [ { "gen": { "height": 237261 } } ], "vout": [ { "amount": 100430103880, "target": { "key": "3a92ece12acd33e612d70d7e2c7fe6632e68cf5be32b9ed75fb03996d082f6b3" } } ], "extra": [ 1, 232, 66, 249, 200, 8, 41, 150, 154, 222, 53, 249, 175, 27, 20, 65, 102, 149, 9, 26, 234, 7, 77, 1, 189, 134, 157, 177, 212, 3, 122, 133, 186, 2, 17, 0, 0, 0, 2, 161, 187, 204, 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