Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba3e70cc38b6d02b5fc1ec8cb80f893e8af24d16fb033a7724dd03cca5605e2e

Tx prefix hash: c8ad2839fdb9019dffa246725233fbd4a82eb7292b5dbd731e9fe6b21102a453
Tx public key: 234a92c961badbfd6158b888dcdaeb510f30e866be6a3f5766f0c0529569765d
Timestamp: 1713223424 Timestamp [UCT]: 2024-04-15 23:23:44 Age [y:d:h:m:s]: 01:205:19:46:55
Block: 1001354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405778 RingCT/type: yes/0
Extra: 01234a92c961badbfd6158b888dcdaeb510f30e866be6a3f5766f0c0529569765d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f5f5136abcc8d62615c92af4e828d0ba0f36fc7f4f8b5f81feb3ca1dd7ded8 0.600000000000 1461858 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": 1001364, "vin": [ { "gen": { "height": 1001354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f5f5136abcc8d62615c92af4e828d0ba0f36fc7f4f8b5f81feb3ca1dd7ded8" } } ], "extra": [ 1, 35, 74, 146, 201, 97, 186, 219, 253, 97, 88, 184, 136, 220, 218, 235, 81, 15, 48, 232, 102, 190, 106, 63, 87, 102, 240, 192, 82, 149, 105, 118, 93, 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