Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c57d75174720f2c13df5d82a17bc3eec99dac32754fedf1fabf4f3c2c921997

Tx prefix hash: 31a524cc006a6341e191392c35c9a4de4cd6b64b9c4af66990dd48b7f7c0d152
Tx public key: 920c02d0140c5aab371ecb2143f18a89bec1e84b4177dfa15a9f703446e6759a
Timestamp: 1710999791 Timestamp [UCT]: 2024-03-21 05:43:11 Age [y:d:h:m:s]: 00:359:11:23:27
Block: 982957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257021 RingCT/type: yes/0
Extra: 01920c02d0140c5aab371ecb2143f18a89bec1e84b4177dfa15a9f703446e6759a021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87b04706a56da8e602d5dc2a33d6b3db7bcf855ac7b22480fab2319b17d35f56 0.600000000000 1443074 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": 982967, "vin": [ { "gen": { "height": 982957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87b04706a56da8e602d5dc2a33d6b3db7bcf855ac7b22480fab2319b17d35f56" } } ], "extra": [ 1, 146, 12, 2, 208, 20, 12, 90, 171, 55, 30, 203, 33, 67, 241, 138, 137, 190, 193, 232, 75, 65, 119, 223, 161, 90, 159, 112, 52, 70, 230, 117, 154, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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