Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232a5bc1dc6bd540b4d6387b204693a6f3ec5abe1998b870793ce1fc29740a97

Tx prefix hash: b72aee8655f4e03e6d2815cf933d9a06b7b6d3aa6f47ff2de5ca91942697eb79
Tx public key: 9a7cf2b78f7eb5a6ae3e336f34768d1ffd16f45bb30cfa92cedd0e9f1dbb023f
Timestamp: 1577154798 Timestamp [UCT]: 2019-12-24 02:33:18 Age [y:d:h:m:s]: 05:012:21:19:43
Block: 30276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159370 RingCT/type: yes/0
Extra: 019a7cf2b78f7eb5a6ae3e336f34768d1ffd16f45bb30cfa92cedd0e9f1dbb023f021100000001d81c26c0000000000000000000

1 output(s) for total of 487.173779399000 dcy

stealth address amount amount idx
00: 049e57131a9499e2f4955a41370e62c61c8ca18010418896c94d884eb699f61d 487.173779399000 49990 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": 30286, "vin": [ { "gen": { "height": 30276 } } ], "vout": [ { "amount": 487173779399, "target": { "key": "049e57131a9499e2f4955a41370e62c61c8ca18010418896c94d884eb699f61d" } } ], "extra": [ 1, 154, 124, 242, 183, 143, 126, 181, 166, 174, 62, 51, 111, 52, 118, 141, 31, 253, 22, 244, 91, 179, 12, 250, 146, 206, 221, 14, 159, 29, 187, 2, 63, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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