Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f43b674f4de09d55138aa783a6c740db945a4d6cbadc9f11a7d5724c15029b95

Tx prefix hash: cc5be41fc3e581080a864c3116f614c999a5f28aca7b1a0dda8ab9ebdf34f9c2
Tx public key: 0da2122e4df7948c935d302cbff81df0fc23a7a2409801f494890c22fae76a05
Timestamp: 1620501342 Timestamp [UCT]: 2021-05-08 19:15:42 Age [y:d:h:m:s]: 03:203:12:33:58
Block: 256897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 905807 RingCT/type: yes/0
Extra: 010da2122e4df7948c935d302cbff81df0fc23a7a2409801f494890c22fae76a05021100000025b1d898ff000000000000000000

1 output(s) for total of 86.455802901000 dcy

stealth address amount amount idx
00: 0e559e442dd7ca7924ae27b8b8ec5d38df13b36b8e330de1c8b76a835f0b957a 86.455802901000 540658 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": 256907, "vin": [ { "gen": { "height": 256897 } } ], "vout": [ { "amount": 86455802901, "target": { "key": "0e559e442dd7ca7924ae27b8b8ec5d38df13b36b8e330de1c8b76a835f0b957a" } } ], "extra": [ 1, 13, 162, 18, 46, 77, 247, 148, 140, 147, 93, 48, 44, 191, 248, 29, 240, 252, 35, 167, 162, 64, 152, 1, 244, 148, 137, 12, 34, 250, 231, 106, 5, 2, 17, 0, 0, 0, 37, 177, 216, 152, 255, 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