Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa21dfa7bfa63855548601edb684260f281d3b98a515c48c2e501b510c9fe683

Tx prefix hash: 66e5a18f48debc283f7e2730d4abdc660c6af5245d97497f6abaee912bc060ae
Tx public key: b2f8c6e072088f6bb974a68992e9cc85550adfda61baf1a994fc3be460b6eda3
Timestamp: 1635084529 Timestamp [UCT]: 2021-10-24 14:08:49 Age [y:d:h:m:s]: 03:093:11:09:30
Block: 359538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845133 RingCT/type: yes/0
Extra: 01b2f8c6e072088f6bb974a68992e9cc85550adfda61baf1a994fc3be460b6eda30211000000075410958b000000000000000000

1 output(s) for total of 39.509520984000 dcy

stealth address amount amount idx
00: fbe2db2da50c3d7495f9bb8cfab97ef94ba83333d46194acca7b60272464ddee 39.509520984000 732113 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": 359548, "vin": [ { "gen": { "height": 359538 } } ], "vout": [ { "amount": 39509520984, "target": { "key": "fbe2db2da50c3d7495f9bb8cfab97ef94ba83333d46194acca7b60272464ddee" } } ], "extra": [ 1, 178, 248, 198, 224, 114, 8, 143, 107, 185, 116, 166, 137, 146, 233, 204, 133, 85, 10, 223, 218, 97, 186, 241, 169, 148, 252, 59, 228, 96, 182, 237, 163, 2, 17, 0, 0, 0, 7, 84, 16, 149, 139, 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