Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7bf0d33855709d46f13ac237d295a6a71dd74b9cad9d651c2f80d17c86217be

Tx prefix hash: f450861a71eecd7740ecb8dc659d4855ecbe5ba0c7a610ab5a8531cf12da92e7
Tx public key: 78070fef4be5e4bc8e558f89f42b6c0799e2e3157401460f8c5fb534efd58521
Timestamp: 1751871880 Timestamp [UCT]: 2025-07-07 07:04:40 Age [y:d:h:m:s]: 00:136:10:37:29
Block: 1320450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95939 RingCT/type: yes/0
Extra: 0178070fef4be5e4bc8e558f89f42b6c0799e2e3157401460f8c5fb534efd585210211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95e6bc0a1cce901391919255f9d14e1314ba518d54783b5a2cb60dd2f873cf2c 0.600000000000 1808149 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": 1320460, "vin": [ { "gen": { "height": 1320450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95e6bc0a1cce901391919255f9d14e1314ba518d54783b5a2cb60dd2f873cf2c" } } ], "extra": [ 1, 120, 7, 15, 239, 75, 229, 228, 188, 142, 85, 143, 137, 244, 43, 108, 7, 153, 226, 227, 21, 116, 1, 70, 15, 140, 95, 181, 52, 239, 213, 133, 33, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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