Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfee5eefefddf1254877fb1472c579d14acfa489292db9fb1982b55be4a5e90b

Tx prefix hash: 6367aeeae0d9ad03d5c872cfc6aa803fb215c0d862707d56fb039a629b582b80
Tx public key: 08e88f96b54c1d19bfd966614de948b199dfae02aa981564c49079f156e39dd8
Timestamp: 1581641089 Timestamp [UCT]: 2020-02-14 00:44:49 Age [y:d:h:m:s]: 04:327:03:26:15
Block: 64531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125965 RingCT/type: yes/0
Extra: 0108e88f96b54c1d19bfd966614de948b199dfae02aa981564c49079f156e39dd8021100000002026b59f3000000000000000000

1 output(s) for total of 375.130884105000 dcy

stealth address amount amount idx
00: b001e7f8cc8e77a15d8a1e404780775bf737a29ad89f74ef7022fd93415bd33e 375.130884105000 119026 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": 64541, "vin": [ { "gen": { "height": 64531 } } ], "vout": [ { "amount": 375130884105, "target": { "key": "b001e7f8cc8e77a15d8a1e404780775bf737a29ad89f74ef7022fd93415bd33e" } } ], "extra": [ 1, 8, 232, 143, 150, 181, 76, 29, 25, 191, 217, 102, 97, 77, 233, 72, 177, 153, 223, 174, 2, 170, 152, 21, 100, 196, 144, 121, 241, 86, 227, 157, 216, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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