Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41bb10e94993af853b1dc31b931ec6fada33c4416731a983d766ac08e7e1ea45

Tx prefix hash: 7b2e8c831a2fa3f46bfd277ef611554f4701e04677ba593d87a327ab18ea92c4
Tx public key: a79b5efcf4ea0376b63f342d9707a94ca40841cfc1b14df1af64e11981e048b8
Timestamp: 1722267175 Timestamp [UCT]: 2024-07-29 15:32:55 Age [y:d:h:m:s]: 00:179:08:09:44
Block: 1076348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128262 RingCT/type: yes/0
Extra: 01a79b5efcf4ea0376b63f342d9707a94ca40841cfc1b14df1af64e11981e048b8021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca27dbf18736281ab834f10a3eb97b1eeab5df1e8135a185c72016ce7e6f9d75 0.600000000000 1548885 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": 1076358, "vin": [ { "gen": { "height": 1076348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca27dbf18736281ab834f10a3eb97b1eeab5df1e8135a185c72016ce7e6f9d75" } } ], "extra": [ 1, 167, 155, 94, 252, 244, 234, 3, 118, 182, 63, 52, 45, 151, 7, 169, 76, 164, 8, 65, 207, 193, 177, 77, 241, 175, 100, 225, 25, 129, 224, 72, 184, 2, 17, 0, 0, 0, 9, 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