Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f0576c4971c0bb510a812e2a77cff152c5b06010b50ad4796673a1d6cf499f7

Tx prefix hash: 866fdda95dc0e1f467e38c5e70c624899801920519ef997630290c6808045ec2
Tx public key: 1b47fa14618dd7cfb5d2cb7c9aa243261c2a309775a42a3bd7aa89e9a9850e3a
Timestamp: 1581140424 Timestamp [UCT]: 2020-02-08 05:40:24 Age [y:d:h:m:s]: 05:271:09:27:11
Block: 60815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1344047 RingCT/type: yes/0
Extra: 011b47fa14618dd7cfb5d2cb7c9aa243261c2a309775a42a3bd7aa89e9a9850e3a0211000000184943cd9f000000000000000000

1 output(s) for total of 385.931722062000 dcy

stealth address amount amount idx
00: b3529b4af057f6064a7c8a1bc46b40ab26ccde1788ba512ac585099d7b8ec8f4 385.931722062000 112032 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": 60825, "vin": [ { "gen": { "height": 60815 } } ], "vout": [ { "amount": 385931722062, "target": { "key": "b3529b4af057f6064a7c8a1bc46b40ab26ccde1788ba512ac585099d7b8ec8f4" } } ], "extra": [ 1, 27, 71, 250, 20, 97, 141, 215, 207, 181, 210, 203, 124, 154, 162, 67, 38, 28, 42, 48, 151, 117, 164, 42, 59, 215, 170, 137, 233, 169, 133, 14, 58, 2, 17, 0, 0, 0, 24, 73, 67, 205, 159, 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