Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229569551f9fa69c69a4ba6cbf6e85aef0a1ab90867b53b4c0918b943afe3df7

Tx prefix hash: 049d307258107947fe8fb9048bf5fa0435cf4eacf6c4129c1cfe08bcc94252e4
Tx public key: eb3ef65fe9f7423dfca4613d2d0ec4fb6ee4affa5a5af5aae0ad35e06debeae9
Timestamp: 1740784768 Timestamp [UCT]: 2025-02-28 23:19:28 Age [y:d:h:m:s]: 00:266:01:12:06
Block: 1229402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187905 RingCT/type: yes/0
Extra: 01eb3ef65fe9f7423dfca4613d2d0ec4fb6ee4affa5a5af5aae0ad35e06debeae9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb5381d674da4455b4d945f095689c29c25be8d2198ad101d8d0a1c9068baa09 0.600000000000 1716289 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": 1229412, "vin": [ { "gen": { "height": 1229402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb5381d674da4455b4d945f095689c29c25be8d2198ad101d8d0a1c9068baa09" } } ], "extra": [ 1, 235, 62, 246, 95, 233, 247, 66, 61, 252, 164, 97, 61, 45, 14, 196, 251, 110, 228, 175, 250, 90, 90, 245, 170, 224, 173, 53, 224, 109, 235, 234, 233, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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