Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca1275a270a065cf16e28191e7cc039e3f58e30a211d8593d9b64ea2a9ca779

Tx prefix hash: c1e5e0ce1ebe7f0ea8a688422671a477cef84ef9b6fe20db013a722e3312eab6
Tx public key: f97984f0a43caf511cdea4c89437592696a1598616f5caa94148137b5d7947fa
Timestamp: 1735922503 Timestamp [UCT]: 2025-01-03 16:41:43 Age [y:d:h:m:s]: 00:308:21:33:24
Block: 1189438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218259 RingCT/type: yes/0
Extra: 01f97984f0a43caf511cdea4c89437592696a1598616f5caa94148137b5d7947fa0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 041bb6f42faed01a9492b48f338f315fc3fcfcd900840f4f1e51415f1c34d3e7 0.600000000000 1675947 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": 1189448, "vin": [ { "gen": { "height": 1189438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "041bb6f42faed01a9492b48f338f315fc3fcfcd900840f4f1e51415f1c34d3e7" } } ], "extra": [ 1, 249, 121, 132, 240, 164, 60, 175, 81, 28, 222, 164, 200, 148, 55, 89, 38, 150, 161, 89, 134, 22, 245, 202, 169, 65, 72, 19, 123, 93, 121, 71, 250, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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