Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333ca8212649dd4f062728bdbb5ef977e4173ea8c0e89e6ea589275cb500b0d8

Tx prefix hash: aaeb805e3784e2743ec4904f8f48160ef37716e2edb1965a55d66702602985b5
Tx public key: c0f916d066e040b95a5d612044a2a4479773e60727eb5abeef8896ce2bb34607
Timestamp: 1635061580 Timestamp [UCT]: 2021-10-24 07:46:20 Age [y:d:h:m:s]: 03:141:05:50:40
Block: 359363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879075 RingCT/type: yes/0
Extra: 01c0f916d066e040b95a5d612044a2a4479773e60727eb5abeef8896ce2bb346070211000000068d0de867000000000000000000

1 output(s) for total of 39.562307317000 dcy

stealth address amount amount idx
00: c4f553d598877630265f6fabbdc1d6979647510ff8e7aee0d7bed79af7ddb8d8 39.562307317000 731830 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": 359373, "vin": [ { "gen": { "height": 359363 } } ], "vout": [ { "amount": 39562307317, "target": { "key": "c4f553d598877630265f6fabbdc1d6979647510ff8e7aee0d7bed79af7ddb8d8" } } ], "extra": [ 1, 192, 249, 22, 208, 102, 224, 64, 185, 90, 93, 97, 32, 68, 162, 164, 71, 151, 115, 230, 7, 39, 235, 90, 190, 239, 136, 150, 206, 43, 179, 70, 7, 2, 17, 0, 0, 0, 6, 141, 13, 232, 103, 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