Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 017dc34de59e6cb7cd7f374359487e9237c4c9a25bbefe2148bf7e950605e2db

Tx prefix hash: 0d292f34e5ce67c2a23daa0ebd39d17f00c83ba8b26cb602156560eb2977fddb
Tx public key: 09af5675b870275aa5c19444b457c43d4a11bcdeca51c2d25226b3b67f3850ab
Timestamp: 1703313202 Timestamp [UCT]: 2023-12-23 06:33:22 Age [y:d:h:m:s]: 01:109:06:12:56
Block: 919223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339199 RingCT/type: yes/0
Extra: 0109af5675b870275aa5c19444b457c43d4a11bcdeca51c2d25226b3b67f3850ab02110000000f46113aa8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 357f7816722a405f1f1a9110a553960cab227b8d34fc04471d805b05e08a7fb3 0.600000000000 1376889 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": 919233, "vin": [ { "gen": { "height": 919223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "357f7816722a405f1f1a9110a553960cab227b8d34fc04471d805b05e08a7fb3" } } ], "extra": [ 1, 9, 175, 86, 117, 184, 112, 39, 90, 165, 193, 148, 68, 180, 87, 196, 61, 74, 17, 188, 222, 202, 81, 194, 210, 82, 38, 179, 182, 127, 56, 80, 171, 2, 17, 0, 0, 0, 15, 70, 17, 58, 168, 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