Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583eabd877230cbdf8f4bb108c4ec2cdabb00d57a84a7aa22d3aa37863ce6163

Tx prefix hash: 6adecb1986dcfb011dd1f9cd6c19219599a15caf7a42b6d5c33e1bca6e59ea27
Tx public key: 1e6b59598b2029db5b1ab715c27cef06c3727848b6f792550854ab9f5702dc09
Timestamp: 1709172666 Timestamp [UCT]: 2024-02-29 02:11:06 Age [y:d:h:m:s]: 01:025:11:39:23
Block: 967792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279221 RingCT/type: yes/0
Extra: 011e6b59598b2029db5b1ab715c27cef06c3727848b6f792550854ab9f5702dc0902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de49b4c9c57cb33ff15502c9a6b738a94a1359a5727f56c417d682f0c4c4e6ad 0.600000000000 1427577 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": 967802, "vin": [ { "gen": { "height": 967792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de49b4c9c57cb33ff15502c9a6b738a94a1359a5727f56c417d682f0c4c4e6ad" } } ], "extra": [ 1, 30, 107, 89, 89, 139, 32, 41, 219, 91, 26, 183, 21, 194, 124, 239, 6, 195, 114, 120, 72, 182, 247, 146, 85, 8, 84, 171, 159, 87, 2, 220, 9, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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