Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67096a970e77ab12542328f1ff5f479bf001e30318c827b75821f2dac6954595

Tx prefix hash: e51d3c764377b1311259798db594c730d8f86c051fb14dc15a525d482988a2c8
Tx public key: 36164295c6b7ebad9fefcab5db11ef9545379bf27c284df25a1488245600e2dc
Timestamp: 1581203661 Timestamp [UCT]: 2020-02-08 23:14:21 Age [y:d:h:m:s]: 05:001:03:00:12
Block: 60943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153541 RingCT/type: yes/0
Extra: 0136164295c6b7ebad9fefcab5db11ef9545379bf27c284df25a1488245600e2dc02110000002b8a2ee0d9000000000000000000

1 output(s) for total of 385.541701156000 dcy

stealth address amount amount idx
00: 3ddd088d2047a3d138ebad0e3ba502071a7004946d3a9fd805d522d92beab0a1 385.541701156000 112340 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": 60953, "vin": [ { "gen": { "height": 60943 } } ], "vout": [ { "amount": 385541701156, "target": { "key": "3ddd088d2047a3d138ebad0e3ba502071a7004946d3a9fd805d522d92beab0a1" } } ], "extra": [ 1, 54, 22, 66, 149, 198, 183, 235, 173, 159, 239, 202, 181, 219, 17, 239, 149, 69, 55, 155, 242, 124, 40, 77, 242, 90, 20, 136, 36, 86, 0, 226, 220, 2, 17, 0, 0, 0, 43, 138, 46, 224, 217, 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