Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d6955f9f01db40f531c75fceb4900e8aeeaf02090b049a741850b8806a6e21

Tx prefix hash: 601f202a5cd296b7ce0492a67c432594d0cf50ce1f5f0d935db454caec3f6c5f
Tx public key: 32a150324e27773fbfeb3ed859ab043af22d20df4fb3bff0b54c437e8355355c
Timestamp: 1715638076 Timestamp [UCT]: 2024-05-13 22:07:56 Age [y:d:h:m:s]: 00:256:22:57:54
Block: 1021390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183862 RingCT/type: yes/0
Extra: 0132a150324e27773fbfeb3ed859ab043af22d20df4fb3bff0b54c437e8355355c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a30686f4a9683fa3343d7275ea531f9ca272dbb80b98cca5fd8ff6c35c477bc0 0.600000000000 1485699 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": 1021400, "vin": [ { "gen": { "height": 1021390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30686f4a9683fa3343d7275ea531f9ca272dbb80b98cca5fd8ff6c35c477bc0" } } ], "extra": [ 1, 50, 161, 80, 50, 78, 39, 119, 63, 191, 235, 62, 216, 89, 171, 4, 58, 242, 45, 32, 223, 79, 179, 191, 240, 181, 76, 67, 126, 131, 85, 53, 92, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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