Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ba2f9e17caae1d94727a44a06d2f329a05191fce6d929ca0e7a18b8313f8555

Tx prefix hash: 17d6b75c7cde549791d5a6f8bb503fd7df015a90c7dead33a709017bcc11c54b
Tx public key: 1a48f4c896cccdd9e6596cf29e9755202379c99204284c572916628be3a2acb3
Timestamp: 1696865088 Timestamp [UCT]: 2023-10-09 15:24:48 Age [y:d:h:m:s]: 01:213:17:03:22
Block: 865969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413789 RingCT/type: yes/0
Extra: 011a48f4c896cccdd9e6596cf29e9755202379c99204284c572916628be3a2acb302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.829249571000 dcy

stealth address amount amount idx
00: 6cd530cbcca8cefc9e26dcc221d02113ae36d5b7c52102ec70907474b526a39e 0.829249571000 1320535 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": 865979, "vin": [ { "gen": { "height": 865969 } } ], "vout": [ { "amount": 829249571, "target": { "key": "6cd530cbcca8cefc9e26dcc221d02113ae36d5b7c52102ec70907474b526a39e" } } ], "extra": [ 1, 26, 72, 244, 200, 150, 204, 205, 217, 230, 89, 108, 242, 158, 151, 85, 32, 35, 121, 201, 146, 4, 40, 76, 87, 41, 22, 98, 139, 227, 162, 172, 179, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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