Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c9cf5fbd22852be25d7d332841fe7c7a6af06457e5ef62eabbb65b0900a65e7

Tx prefix hash: c346f3ac6dbf98cceef1608486e853ec95995c0a3ec5c8df9c5acfddac6a06fe
Tx public key: f901ceb39750f292474e2f411cef06d9e037c03be8897d118a7143bf05450eb8
Timestamp: 1720525121 Timestamp [UCT]: 2024-07-09 11:38:41 Age [y:d:h:m:s]: 00:345:04:38:14
Block: 1061915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246559 RingCT/type: yes/0
Extra: 01f901ceb39750f292474e2f411cef06d9e037c03be8897d118a7143bf05450eb802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd887a4e1fd0d8fbda099221ddeddb5f3a080cd2b246fd00f5a36522f77411a8 0.600000000000 1532414 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": 1061925, "vin": [ { "gen": { "height": 1061915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd887a4e1fd0d8fbda099221ddeddb5f3a080cd2b246fd00f5a36522f77411a8" } } ], "extra": [ 1, 249, 1, 206, 179, 151, 80, 242, 146, 71, 78, 47, 65, 28, 239, 6, 217, 224, 55, 192, 59, 232, 137, 125, 17, 138, 113, 67, 191, 5, 69, 14, 184, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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