Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe73cef4fe2602f23264c56b0209f0524a35d930f58f5cb292ec6e817232c6f1

Tx prefix hash: e54995ff41ae6d3bde49c84a0d83a3a358520002bf3cfe2e0dda8ffe1a66c8c0
Tx public key: f70e60b504a071b3a429d1e96302082908668c2f5a792ea2b26e90005a7eddc8
Timestamp: 1704685254 Timestamp [UCT]: 2024-01-08 03:40:54 Age [y:d:h:m:s]: 01:092:00:01:42
Block: 930564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326867 RingCT/type: yes/0
Extra: 01f70e60b504a071b3a429d1e96302082908668c2f5a792ea2b26e90005a7eddc80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9bcd81ee9d58d348b3a2e262f16c6f32c5365a3105c30628b573b2d52799ec5 0.600000000000 1388446 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": 930574, "vin": [ { "gen": { "height": 930564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9bcd81ee9d58d348b3a2e262f16c6f32c5365a3105c30628b573b2d52799ec5" } } ], "extra": [ 1, 247, 14, 96, 181, 4, 160, 113, 179, 164, 41, 209, 233, 99, 2, 8, 41, 8, 102, 140, 47, 90, 121, 46, 162, 178, 110, 144, 0, 90, 126, 221, 200, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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