Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6afb08dc8fc1e23a54f1600eae447031499710a5f7aa0c3b0f71e76b79ff2b1

Tx prefix hash: ff7c5c8fc1d4ef07db0bbbcfa7fb99fac533debe50e47ec61dc3a0e40546800d
Tx public key: 2804ae82a847bee60fe4ca00999a39faaf7679001e416e2d0b467dda29ecb141
Timestamp: 1588902514 Timestamp [UCT]: 2020-05-08 01:48:34 Age [y:d:h:m:s]: 04:137:10:52:50
Block: 99743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1015211 RingCT/type: yes/0
Extra: 012804ae82a847bee60fe4ca00999a39faaf7679001e416e2d0b467dda29ecb1410211000000756fa03929000000000000000000

1 output(s) for total of 286.754867142000 dcy

stealth address amount amount idx
00: 11c957d74f3a16fdb18a3c2afb80b36980f05faba9c96e55a8707d1c148e2339 286.754867142000 175883 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": 99753, "vin": [ { "gen": { "height": 99743 } } ], "vout": [ { "amount": 286754867142, "target": { "key": "11c957d74f3a16fdb18a3c2afb80b36980f05faba9c96e55a8707d1c148e2339" } } ], "extra": [ 1, 40, 4, 174, 130, 168, 71, 190, 230, 15, 228, 202, 0, 153, 154, 57, 250, 175, 118, 121, 0, 30, 65, 110, 45, 11, 70, 125, 218, 41, 236, 177, 65, 2, 17, 0, 0, 0, 117, 111, 160, 57, 41, 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