Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad92a47d08534b598987035a173d8fdafaa51248bdb531f7226a0c7c598375c

Tx prefix hash: d79b42120157baba1e8f2db26787217f0dda79043b2e91d52102dc8766aa33c6
Tx public key: e9e75aef5d8b950d2755352d0425a22fa6bbae53a8a0833d4d79b235dd2d0b87
Timestamp: 1644991203 Timestamp [UCT]: 2022-02-16 06:00:03 Age [y:d:h:m:s]: 02:288:21:46:01
Block: 439670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725770 RingCT/type: yes/0
Extra: 01e9e75aef5d8b950d2755352d0425a22fa6bbae53a8a0833d4d79b235dd2d0b87021100000014bf7ee4e7000000000000000000

1 output(s) for total of 21.440475750000 dcy

stealth address amount amount idx
00: 7bb6da84ca709ce95daeeb2e2ec5496ee8df0a37789c9b64c84ff0be8ac088f1 21.440475750000 851837 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": 439680, "vin": [ { "gen": { "height": 439670 } } ], "vout": [ { "amount": 21440475750, "target": { "key": "7bb6da84ca709ce95daeeb2e2ec5496ee8df0a37789c9b64c84ff0be8ac088f1" } } ], "extra": [ 1, 233, 231, 90, 239, 93, 139, 149, 13, 39, 85, 53, 45, 4, 37, 162, 47, 166, 187, 174, 83, 168, 160, 131, 61, 77, 121, 178, 53, 221, 45, 11, 135, 2, 17, 0, 0, 0, 20, 191, 126, 228, 231, 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