Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e4ef0650628fbdd76777153af045b0abab8f0d14c375472a129fe4f24fd154b

Tx prefix hash: b9615447903365ae5ea785020af14b2b8fbe63fa7e1f752a24d0e79a30921648
Tx public key: 489d41b334b60eb0b020ad886d54b94e36df4f69883994278bb57bb593cf0b1b
Timestamp: 1616606728 Timestamp [UCT]: 2021-03-24 17:25:28 Age [y:d:h:m:s]: 03:226:22:59:22
Block: 225599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 921603 RingCT/type: yes/0
Extra: 01489d41b334b60eb0b020ad886d54b94e36df4f69883994278bb57bb593cf0b1b021100000033a9e81d35000000000000000000

1 output(s) for total of 109.778494583000 dcy

stealth address amount amount idx
00: 348ba1dd2d0e9f488807b6ee19578bffc8a6e0291d13709c8067d7182f38d0c0 109.778494583000 466665 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": 225609, "vin": [ { "gen": { "height": 225599 } } ], "vout": [ { "amount": 109778494583, "target": { "key": "348ba1dd2d0e9f488807b6ee19578bffc8a6e0291d13709c8067d7182f38d0c0" } } ], "extra": [ 1, 72, 157, 65, 179, 52, 182, 14, 176, 176, 32, 173, 136, 109, 84, 185, 78, 54, 223, 79, 105, 136, 57, 148, 39, 139, 181, 123, 181, 147, 207, 11, 27, 2, 17, 0, 0, 0, 51, 169, 232, 29, 53, 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