Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e347dcd0c23a53aa085319433ec1976bc712bd39a6e89c17f4916f794456037

Tx prefix hash: aac11076e034396c1fb95acacc7ef46403314b45a63cfe61a4585f7bd1063616
Tx public key: e2e9f3a91c977b42b02add0479db9400e2698c991cbf164e924629c813483ece
Timestamp: 1581240318 Timestamp [UCT]: 2020-02-09 09:25:18 Age [y:d:h:m:s]: 05:023:11:34:59
Block: 61164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169610 RingCT/type: yes/0
Extra: 01e2e9f3a91c977b42b02add0479db9400e2698c991cbf164e924629c813483ece02110000002e026b59f3000000000000000000

1 output(s) for total of 384.898836011000 dcy

stealth address amount amount idx
00: 53945e882612ce8a78c3fb2e56c0661a0b7825a99160d6b407b527ae6253524f 384.898836011000 112715 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": 61174, "vin": [ { "gen": { "height": 61164 } } ], "vout": [ { "amount": 384898836011, "target": { "key": "53945e882612ce8a78c3fb2e56c0661a0b7825a99160d6b407b527ae6253524f" } } ], "extra": [ 1, 226, 233, 243, 169, 28, 151, 123, 66, 176, 42, 221, 4, 121, 219, 148, 0, 226, 105, 140, 153, 28, 191, 22, 78, 146, 70, 41, 200, 19, 72, 62, 206, 2, 17, 0, 0, 0, 46, 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