Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fe7c06eff7717f0aec861a175d7a909e5eb78284f384e14121f9261bea1961

Tx prefix hash: f59084fc57d93a721b97633bb7ecbde576c819221bc9a2cb5dfc4a31dbba4321
Tx public key: e5b33f71dad89e40f8dfced3b9831c0ad1ed8535c1adb559b8fbfc7f5f292271
Timestamp: 1574097196 Timestamp [UCT]: 2019-11-18 17:13:16 Age [y:d:h:m:s]: 05:175:17:37:58
Block: 11887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1268654 RingCT/type: yes/0
Extra: 01e5b33f71dad89e40f8dfced3b9831c0ad1ed8535c1adb559b8fbfc7f5f29227102110000000166a80d00000000000000000000

1 output(s) for total of 560.549956481000 dcy

stealth address amount amount idx
00: 1d7d8543e2ea67c24ac8e29169b12f8314e670e84b81697d94756280ee3a3513 560.549956481000 12972 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": 11897, "vin": [ { "gen": { "height": 11887 } } ], "vout": [ { "amount": 560549956481, "target": { "key": "1d7d8543e2ea67c24ac8e29169b12f8314e670e84b81697d94756280ee3a3513" } } ], "extra": [ 1, 229, 179, 63, 113, 218, 216, 158, 64, 248, 223, 206, 211, 185, 131, 28, 10, 209, 237, 133, 53, 193, 173, 181, 89, 184, 251, 252, 127, 95, 41, 34, 113, 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