Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0417d634dc49784429d9c115a033052197b8cd4ef85f66075fbbb48dad9d9f

Tx prefix hash: 7ff6750134838d28a30ab154e6189c83eb6162d3b5c6b20eca4762e239550c47
Tx public key: 3757fe1f9581407e1e8ff65743f8ec210d1b0a9e2f93eea7e64831c370e983f5
Timestamp: 1710435990 Timestamp [UCT]: 2024-03-14 17:06:30 Age [y:d:h:m:s]: 01:078:05:18:15
Block: 978288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316916 RingCT/type: yes/0
Extra: 013757fe1f9581407e1e8ff65743f8ec210d1b0a9e2f93eea7e64831c370e983f50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7a9d08d7383945be3683797c3b19a510bdb62ce8145b7780cd37874e7c0d7a 0.600000000000 1438311 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": 978298, "vin": [ { "gen": { "height": 978288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7a9d08d7383945be3683797c3b19a510bdb62ce8145b7780cd37874e7c0d7a" } } ], "extra": [ 1, 55, 87, 254, 31, 149, 129, 64, 126, 30, 143, 246, 87, 67, 248, 236, 33, 13, 27, 10, 158, 47, 147, 238, 167, 230, 72, 49, 195, 112, 233, 131, 245, 2, 17, 0, 0, 0, 2, 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