Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3024f44296339b44626ecd918e0354c1c3cadb802ca12a617d5a79fccbc19f89

Tx prefix hash: 4ec875f29cb9a613d0116c766291e43ca0fba2c4f5ae8b9bfb3a3b91def33ed2
Tx public key: 990f518d06d854e7f4d1b2cf90da8347cacf1c168849b97ecb00429e78ef45bf
Timestamp: 1731080843 Timestamp [UCT]: 2024-11-08 15:47:23 Age [y:d:h:m:s]: 00:221:07:01:13
Block: 1149343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157899 RingCT/type: yes/0
Extra: 01990f518d06d854e7f4d1b2cf90da8347cacf1c168849b97ecb00429e78ef45bf0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51f21869ce42b1eede2c36ac29e7a4766d0287df1f79dd1ecf6292b62e40fd0d 0.600000000000 1634404 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": 1149353, "vin": [ { "gen": { "height": 1149343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51f21869ce42b1eede2c36ac29e7a4766d0287df1f79dd1ecf6292b62e40fd0d" } } ], "extra": [ 1, 153, 15, 81, 141, 6, 216, 84, 231, 244, 209, 178, 207, 144, 218, 131, 71, 202, 207, 28, 22, 136, 73, 185, 126, 203, 0, 66, 158, 120, 239, 69, 191, 2, 17, 0, 0, 0, 3, 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