Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aada393c3e5981e99f19fbfc7659125401c7dec39a77e9d0928749a222e32a60

Tx prefix hash: 07e998598b319aebf0ee04143443ddd43607451f5107acf9d38d0be7d214571a
Tx public key: 61d5f7aa13910a37976cf11aef0ce62ec6c7e8d15ddea19ff2cda611423e97aa
Timestamp: 1581651749 Timestamp [UCT]: 2020-02-14 03:42:29 Age [y:d:h:m:s]: 05:116:00:10:17
Block: 64619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235750 RingCT/type: yes/0
Extra: 0161d5f7aa13910a37976cf11aef0ce62ec6c7e8d15ddea19ff2cda611423e97aa0211000000024ac5aa02000000000000000000

1 output(s) for total of 374.879109779000 dcy

stealth address amount amount idx
00: deae1862c34da207cde9f05d3f25239c1b566102806203ea716071f59cba7ae4 374.879109779000 119199 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": 64629, "vin": [ { "gen": { "height": 64619 } } ], "vout": [ { "amount": 374879109779, "target": { "key": "deae1862c34da207cde9f05d3f25239c1b566102806203ea716071f59cba7ae4" } } ], "extra": [ 1, 97, 213, 247, 170, 19, 145, 10, 55, 151, 108, 241, 26, 239, 12, 230, 46, 198, 199, 232, 209, 93, 222, 161, 159, 242, 205, 166, 17, 66, 62, 151, 170, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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