Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca212432d6a3a56dce05ae3bd3a058099d941f54e9249950ba080ddc9789c2f

Tx prefix hash: 85a4f913e52e317cf522c945c315cc9479759a7d0860fd76006074f39c203bd0
Tx public key: 99c0409cd42d1eb0be427b284166c21bdee9f6bc5c7930b30b7e22da9e537337
Timestamp: 1729275535 Timestamp [UCT]: 2024-10-18 18:18:55 Age [y:d:h:m:s]: 00:004:08:14:20
Block: 1134463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3072 RingCT/type: yes/0
Extra: 0199c0409cd42d1eb0be427b284166c21bdee9f6bc5c7930b30b7e22da9e5373370211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be7458f6934ebc8c26781d6e536f8c335a8d4adbab98995b7e18a1015db7257 0.600000000000 1617770 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": 1134473, "vin": [ { "gen": { "height": 1134463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be7458f6934ebc8c26781d6e536f8c335a8d4adbab98995b7e18a1015db7257" } } ], "extra": [ 1, 153, 192, 64, 156, 212, 45, 30, 176, 190, 66, 123, 40, 65, 102, 194, 27, 222, 233, 246, 188, 92, 121, 48, 179, 11, 126, 34, 218, 158, 83, 115, 55, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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