Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a040760d7f2068a77927606020e631dea806cd96f15ab26307277d03ccf813

Tx prefix hash: 048b62cfb87eb59e8a5847f33ec2dc1a4bfdf5050ff004cfbf759d8763254d1b
Tx public key: 6697278d71c531ea792ffb55e29fafb2e20179ba323f29db7e54045d6f4e875b
Timestamp: 1713104170 Timestamp [UCT]: 2024-04-14 14:16:10 Age [y:d:h:m:s]: 01:203:19:04:08
Block: 1000367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404326 RingCT/type: yes/0
Extra: 016697278d71c531ea792ffb55e29fafb2e20179ba323f29db7e54045d6f4e875b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4db7f7fbce48053979c4980aded7a6c1dc8ae5a67ab6516028169686dae00e7a 0.600000000000 1460865 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": 1000377, "vin": [ { "gen": { "height": 1000367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4db7f7fbce48053979c4980aded7a6c1dc8ae5a67ab6516028169686dae00e7a" } } ], "extra": [ 1, 102, 151, 39, 141, 113, 197, 49, 234, 121, 47, 251, 85, 226, 159, 175, 178, 226, 1, 121, 186, 50, 63, 41, 219, 126, 84, 4, 93, 111, 78, 135, 91, 2, 17, 0, 0, 0, 1, 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