Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3219d62f80553852b42fabb9b5d25f51f56ff9c3aca7de51f34b5e40f75b33

Tx prefix hash: 45fa8511878e13b41d3ec4afa783dc6f8b39c1b7a37c41949314f7009b1e6eb7
Tx public key: 492a59ef46d756829040e6b1c5aaabd2fdf73b8423c841a4c166f8aa171ec185
Timestamp: 1726734101 Timestamp [UCT]: 2024-09-19 08:21:41 Age [y:d:h:m:s]: 01:019:16:30:17
Block: 1113376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272446 RingCT/type: yes/0
Extra: 01492a59ef46d756829040e6b1c5aaabd2fdf73b8423c841a4c166f8aa171ec1850211000000015a5c538d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 730c1fcc349a5e10f5186aee21acdec18cca47d35320c84afc0f8d5451a643a2 0.600000000000 1593031 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": 1113386, "vin": [ { "gen": { "height": 1113376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "730c1fcc349a5e10f5186aee21acdec18cca47d35320c84afc0f8d5451a643a2" } } ], "extra": [ 1, 73, 42, 89, 239, 70, 215, 86, 130, 144, 64, 230, 177, 197, 170, 171, 210, 253, 247, 59, 132, 35, 200, 65, 164, 193, 102, 248, 170, 23, 30, 193, 133, 2, 17, 0, 0, 0, 1, 90, 92, 83, 141, 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