Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3170561979fd51106fd4a9e2f1c210ef83dc476107346a825b276e8ec4fbe8a1

Tx prefix hash: 421bd9a6ed624d2f48f55c50593ce73f250108adcae300eea4b7e1ca81a252cf
Tx public key: 287eb7621ad31cb599ed9e2e9546bf79f0e045448168a5e19d5603e1e3da3009
Timestamp: 1709911265 Timestamp [UCT]: 2024-03-08 15:21:05 Age [y:d:h:m:s]: 01:251:09:35:38
Block: 973919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438398 RingCT/type: yes/0
Extra: 01287eb7621ad31cb599ed9e2e9546bf79f0e045448168a5e19d5603e1e3da300902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48d730b65d960ee0c7fc2d034ca239d91b08e32c43ae20fc8115667611c2c070 0.600000000000 1433862 of 15

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": 973929, "vin": [ { "gen": { "height": 973919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48d730b65d960ee0c7fc2d034ca239d91b08e32c43ae20fc8115667611c2c070" } } ], "extra": [ 1, 40, 126, 183, 98, 26, 211, 28, 181, 153, 237, 158, 46, 149, 70, 191, 121, 240, 224, 69, 68, 129, 104, 165, 225, 157, 86, 3, 225, 227, 218, 48, 9, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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