Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1493d907a8552f195c6a13f95a410bfc1dbcbd6ddce3d23cf1a06f9b816681

Tx prefix hash: 9261d065f5dd60684eeb6579112de15fb480c326ddc4a2c4fd72541192b32262
Tx public key: ffa8b90d7495349b9677a8f1c3c5fd60399893dc7589f6e671708907e99d3101
Timestamp: 1713510777 Timestamp [UCT]: 2024-04-19 07:12:57 Age [y:d:h:m:s]: 00:210:03:39:59
Block: 1003751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150447 RingCT/type: yes/0
Extra: 01ffa8b90d7495349b9677a8f1c3c5fd60399893dc7589f6e671708907e99d31010211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f09a5ac16deea89d2b79e34a6b3e32cd50daa5154d13cf6877dcf1260a13952d 0.600000000000 1464293 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": 1003761, "vin": [ { "gen": { "height": 1003751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f09a5ac16deea89d2b79e34a6b3e32cd50daa5154d13cf6877dcf1260a13952d" } } ], "extra": [ 1, 255, 168, 185, 13, 116, 149, 52, 155, 150, 119, 168, 241, 195, 197, 253, 96, 57, 152, 147, 220, 117, 137, 246, 230, 113, 112, 137, 7, 233, 157, 49, 1, 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