Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84f8a75c7842b1d8e121d07df3ff157e792cba2ad0d493af149fa0a4875ee4b

Tx prefix hash: 7df4e743ca396f01fdd478dcc044f14c91e5b6f7c7cb6fe45bdddd59dfc615a1
Tx public key: cd8010afd09503649f1f288d4cc2ea1a641394be43c5912dd874361f1f739db5
Timestamp: 1737971535 Timestamp [UCT]: 2025-01-27 09:52:15 Age [y:d:h:m:s]: 00:339:14:33:51
Block: 1206151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240523 RingCT/type: yes/0
Extra: 01cd8010afd09503649f1f288d4cc2ea1a641394be43c5912dd874361f1f739db50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8552e04c62c7fe856cacf1ee91f0c7e2622bb46503f27110b62ef86d9a84e0d9 0.600000000000 1692854 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": 1206161, "vin": [ { "gen": { "height": 1206151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8552e04c62c7fe856cacf1ee91f0c7e2622bb46503f27110b62ef86d9a84e0d9" } } ], "extra": [ 1, 205, 128, 16, 175, 208, 149, 3, 100, 159, 31, 40, 141, 76, 194, 234, 26, 100, 19, 148, 190, 67, 197, 145, 45, 216, 116, 54, 31, 31, 115, 157, 181, 2, 17, 0, 0, 0, 1, 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