Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a660ac5f1c0492bd39e4298e3f0ffb71e7640795494c0877b23cbb9dae6abf8

Tx prefix hash: c59b60d7c62a934c2b18b37e293dabef1eba340eb63df2ef17820596e5ef8d17
Tx public key: fd90747709e29843bc833212cacb4c2aa030093c67fe8deb3f94a2d5e9c6577b
Timestamp: 1696775751 Timestamp [UCT]: 2023-10-08 14:35:51 Age [y:d:h:m:s]: 01:249:14:21:30
Block: 865229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439380 RingCT/type: yes/0
Extra: 01fd90747709e29843bc833212cacb4c2aa030093c67fe8deb3f94a2d5e9c6577b02110000000333af99f4000000000000000000

1 output(s) for total of 0.833944567000 dcy

stealth address amount amount idx
00: cc910f802918c025a7550774fb728041c6512c8990010100795bcd2581cd2497 0.833944567000 1319759 of 0

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": 865239, "vin": [ { "gen": { "height": 865229 } } ], "vout": [ { "amount": 833944567, "target": { "key": "cc910f802918c025a7550774fb728041c6512c8990010100795bcd2581cd2497" } } ], "extra": [ 1, 253, 144, 116, 119, 9, 226, 152, 67, 188, 131, 50, 18, 202, 203, 76, 42, 160, 48, 9, 60, 103, 254, 141, 235, 63, 148, 162, 213, 233, 198, 87, 123, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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