Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9bd53a9aa789363ee9042db9af7d8ddb301a4acf23ecc3725c07c2dd9bee882

Tx prefix hash: 14e39d332d7fe686cdbe089e505ccd60397a610f1d452500645cbe5b0a5b4a37
Tx public key: cde8b57348bc3cf3dd9ef1ef184f75ca6d953d5fbf7277de315f80347f5e263a
Timestamp: 1719905854 Timestamp [UCT]: 2024-07-02 07:37:34 Age [y:d:h:m:s]: 00:302:19:12:09
Block: 1056782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216353 RingCT/type: yes/0
Extra: 01cde8b57348bc3cf3dd9ef1ef184f75ca6d953d5fbf7277de315f80347f5e263a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9c41cdc43b81cedeea4c18c075fd92dda9fd3b36cb10dfd33c9e0b79f8a746 0.600000000000 1527211 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": 1056792, "vin": [ { "gen": { "height": 1056782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9c41cdc43b81cedeea4c18c075fd92dda9fd3b36cb10dfd33c9e0b79f8a746" } } ], "extra": [ 1, 205, 232, 181, 115, 72, 188, 60, 243, 221, 158, 241, 239, 24, 79, 117, 202, 109, 149, 61, 95, 191, 114, 119, 222, 49, 95, 128, 52, 127, 94, 38, 58, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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