Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d0059c5f66384b694b5d53d87e8ed82c18274af15de0940a376742285cdd64

Tx prefix hash: 380b00e139f24f0e67f556cda6d163b7082dc1b60fb3949c5c8998855a8eac39
Tx public key: d98e6a3a7c98504ee5eff535fc2ef3c1ec6061e75c8d00a5e757890d11d2e828
Timestamp: 1713157434 Timestamp [UCT]: 2024-04-15 05:03:54 Age [y:d:h:m:s]: 01:031:03:29:53
Block: 1000808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283238 RingCT/type: yes/0
Extra: 01d98e6a3a7c98504ee5eff535fc2ef3c1ec6061e75c8d00a5e757890d11d2e82802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16219f74aef8159d2d28a3e74fd0282bc6e5cd09ea9528a03d863086d18234a0 0.600000000000 1461308 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": 1000818, "vin": [ { "gen": { "height": 1000808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16219f74aef8159d2d28a3e74fd0282bc6e5cd09ea9528a03d863086d18234a0" } } ], "extra": [ 1, 217, 142, 106, 58, 124, 152, 80, 78, 229, 239, 245, 53, 252, 46, 243, 193, 236, 96, 97, 231, 92, 141, 0, 165, 231, 87, 137, 13, 17, 210, 232, 40, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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