Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530c65465aceee7c4e4608bbc1baa9ed66ae2c28cec2a688ce07ed71da5724b4

Tx prefix hash: a2816b19381108e179fda657a72331f6ae18850cc3eb3c46714fc7686e0fd61e
Tx public key: 79ef94c274c46c9f3869f3efe8744c8de9a94414c029dc2bed3a02fe97ea3c36
Timestamp: 1716552650 Timestamp [UCT]: 2024-05-24 12:10:50 Age [y:d:h:m:s]: 00:357:17:09:01
Block: 1028991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255674 RingCT/type: yes/0
Extra: 0179ef94c274c46c9f3869f3efe8744c8de9a94414c029dc2bed3a02fe97ea3c360211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ece6f3647e09ef27bd4b496d953a88b039867985a9a3e3cb23f186116b76c44f 0.600000000000 1496992 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": 1029001, "vin": [ { "gen": { "height": 1028991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece6f3647e09ef27bd4b496d953a88b039867985a9a3e3cb23f186116b76c44f" } } ], "extra": [ 1, 121, 239, 148, 194, 116, 196, 108, 159, 56, 105, 243, 239, 232, 116, 76, 141, 233, 169, 68, 20, 192, 41, 220, 43, 237, 58, 2, 254, 151, 234, 60, 54, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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