Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f71f3492e76e8de8e57bb5d51c09ab5b60ed648ad1919816ebda081fe4da765

Tx prefix hash: 0af9903c764a3fe19312a02c1da620a6fb1fcd0cfeec86a9f08c0e5678560cda
Tx public key: 65c75d50404f895ef7a4d41130d4b4f0b1311db3fa10fbc70c854adb13fee2ed
Timestamp: 1722983308 Timestamp [UCT]: 2024-08-06 22:28:28 Age [y:d:h:m:s]: 00:246:08:21:46
Block: 1082280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175970 RingCT/type: yes/0
Extra: 0165c75d50404f895ef7a4d41130d4b4f0b1311db3fa10fbc70c854adb13fee2ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f466c5908b50a88d5de1ea00b49e12421bc60c8a3aed4da7632b6c21f64529e 0.600000000000 1556105 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": 1082290, "vin": [ { "gen": { "height": 1082280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f466c5908b50a88d5de1ea00b49e12421bc60c8a3aed4da7632b6c21f64529e" } } ], "extra": [ 1, 101, 199, 93, 80, 64, 79, 137, 94, 247, 164, 212, 17, 48, 212, 180, 240, 177, 49, 29, 179, 250, 16, 251, 199, 12, 133, 74, 219, 19, 254, 226, 237, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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