Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a76f994b38aba9193c2af56855ab27a3535240c44677c2a58457ad986350e515

Tx prefix hash: 304da3797b9444b256fde76b3308f0c67ef47b0bea4763df961927f479efc426
Tx public key: bb991fc7f5efdd8023160c1a6b2c9f85f4c9610a2c8cbd76bfb2015891b2f5d6
Timestamp: 1735446393 Timestamp [UCT]: 2024-12-29 04:26:33 Age [y:d:h:m:s]: 00:169:04:36:22
Block: 1185479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120648 RingCT/type: yes/0
Extra: 01bb991fc7f5efdd8023160c1a6b2c9f85f4c9610a2c8cbd76bfb2015891b2f5d60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d75d5633f3ff8920684eefaa073afdf79bc2ee3da3d9661d7ebff005c95f9b6 0.600000000000 1671950 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": 1185489, "vin": [ { "gen": { "height": 1185479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d75d5633f3ff8920684eefaa073afdf79bc2ee3da3d9661d7ebff005c95f9b6" } } ], "extra": [ 1, 187, 153, 31, 199, 245, 239, 221, 128, 35, 22, 12, 26, 107, 44, 159, 133, 244, 201, 97, 10, 44, 140, 189, 118, 191, 178, 1, 88, 145, 178, 245, 214, 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