Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86748f20357ce5a772d7e735a5eade8d23ff299c4fe6d35a966a6b2539c4f39c

Tx prefix hash: 658f3496307d64bd29ae5198181ae22925647089b40a1c6720c91c144219ca48
Tx public key: b153d1007f9bea7d67611d849686fb5f1f03f2d2e1093b78b6101479356239af
Timestamp: 1581243947 Timestamp [UCT]: 2020-02-09 10:25:47 Age [y:d:h:m:s]: 04:322:05:34:34
Block: 61224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122457 RingCT/type: yes/0
Extra: 01b153d1007f9bea7d67611d849686fb5f1f03f2d2e1093b78b6101479356239af0211000001c30aca7173000000000000000000

1 output(s) for total of 384.716035999000 dcy

stealth address amount amount idx
00: 63270152b32d9f35b75a3dd46205807d8752ca8264ea117e1e992d04720d017b 384.716035999000 112817 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": 61234, "vin": [ { "gen": { "height": 61224 } } ], "vout": [ { "amount": 384716035999, "target": { "key": "63270152b32d9f35b75a3dd46205807d8752ca8264ea117e1e992d04720d017b" } } ], "extra": [ 1, 177, 83, 209, 0, 127, 155, 234, 125, 103, 97, 29, 132, 150, 134, 251, 95, 31, 3, 242, 210, 225, 9, 59, 120, 182, 16, 20, 121, 53, 98, 57, 175, 2, 17, 0, 0, 1, 195, 10, 202, 113, 115, 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