Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f2831b1ecca1589afbfd27c779ab03e3725c15a1b4a1a3faabde3fa0e38c7b

Tx prefix hash: a0b893d1bb10f8164c9e6e42452699ec4b3a3a06247d8899fb87d57a1c24a4fb
Tx public key: c301cb20b1ff1b970d2cfa157e57f48c6ccfcf9ffe2589ee4ef84a59f74b1875
Timestamp: 1574208982 Timestamp [UCT]: 2019-11-20 00:16:22 Age [y:d:h:m:s]: 05:347:13:29:37
Block: 12863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1389101 RingCT/type: yes/0
Extra: 01c301cb20b1ff1b970d2cfa157e57f48c6ccfcf9ffe2589ee4ef84a59f74b187502110000000166a80d00000000000000000000

1 output(s) for total of 556.403465633000 dcy

stealth address amount amount idx
00: 34d1fc24545d90aa1a44c86adf74452c65b1958f4460e6a6bc5d14a8c31354d3 556.403465633000 14680 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": 12873, "vin": [ { "gen": { "height": 12863 } } ], "vout": [ { "amount": 556403465633, "target": { "key": "34d1fc24545d90aa1a44c86adf74452c65b1958f4460e6a6bc5d14a8c31354d3" } } ], "extra": [ 1, 195, 1, 203, 32, 177, 255, 27, 151, 13, 44, 250, 21, 126, 87, 244, 140, 108, 207, 207, 159, 254, 37, 137, 238, 78, 248, 74, 89, 247, 75, 24, 117, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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