Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34aa63af90a589c84e26ec1dd7ded10f25b091da9dd20df77eb185ed83777d1b

Tx prefix hash: e9c9b0e7e0b94e53b582453336fad9b6f60c632ab78be0d41f6c13b4e473be2c
Tx public key: c3b42ee4c69a6333da846aeb3f83f2cf663bd0a769cf9be89b8347fe422fd2da
Timestamp: 1583236938 Timestamp [UCT]: 2020-03-03 12:02:18 Age [y:d:h:m:s]: 04:297:18:00:34
Block: 75471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107209 RingCT/type: yes/0
Extra: 01c3b42ee4c69a6333da846aeb3f83f2cf663bd0a769cf9be89b8347fe422fd2da0211000001270aca7173000000000000000000

1 output(s) for total of 345.091326640000 dcy

stealth address amount amount idx
00: 6061118aa4a8d07304f36e4d45bbd82918f325dca860a7e6c2b4e670639bed6c 345.091326640000 139415 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": 75481, "vin": [ { "gen": { "height": 75471 } } ], "vout": [ { "amount": 345091326640, "target": { "key": "6061118aa4a8d07304f36e4d45bbd82918f325dca860a7e6c2b4e670639bed6c" } } ], "extra": [ 1, 195, 180, 46, 228, 198, 154, 99, 51, 218, 132, 106, 235, 63, 131, 242, 207, 102, 59, 208, 167, 105, 207, 155, 232, 155, 131, 71, 254, 66, 47, 210, 218, 2, 17, 0, 0, 1, 39, 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