Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ec1e9a9e74e14bfe2130c1bbf8c44b15c6240c2a95742c9c886cb65bb3afcf

Tx prefix hash: 9c3b4df689b160419eea46121c47ba9936c85a109acebdc8016aef0b61417636
Tx public key: 50a4ca8710771912ad48ca9f1c69f6f035ddac6ad434cb7fe99d56b768ab7777
Timestamp: 1700044805 Timestamp [UCT]: 2023-11-15 10:40:05 Age [y:d:h:m:s]: 01:100:05:47:00
Block: 892116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332779 RingCT/type: yes/0
Extra: 0150a4ca8710771912ad48ca9f1c69f6f035ddac6ad434cb7fe99d56b768ab777702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.679290820000 dcy

stealth address amount amount idx
00: 22351839e9a5c8db0ee22622abc4c556d5000d9b9679e82d4b1676db954ddaf3 0.679290820000 1348177 of 0

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": 892126, "vin": [ { "gen": { "height": 892116 } } ], "vout": [ { "amount": 679290820, "target": { "key": "22351839e9a5c8db0ee22622abc4c556d5000d9b9679e82d4b1676db954ddaf3" } } ], "extra": [ 1, 80, 164, 202, 135, 16, 119, 25, 18, 173, 72, 202, 159, 28, 105, 246, 240, 53, 221, 172, 106, 212, 52, 203, 127, 233, 157, 86, 183, 104, 171, 119, 119, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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