Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442412634accd366facf285aa696c7f7c80d92f3c145d50d30a1f52fd710d600

Tx prefix hash: fbca0e292748ce34a552dcf880488d7d6757e3b01e309fb69fb947fc01cb463f
Tx public key: 50ce3b1c26e999b18c10b1ba5ce58081647e7341249ae1f41f19629a209ce403
Timestamp: 1722575277 Timestamp [UCT]: 2024-08-02 05:07:57 Age [y:d:h:m:s]: 00:250:15:07:52
Block: 1078902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179022 RingCT/type: yes/0
Extra: 0150ce3b1c26e999b18c10b1ba5ce58081647e7341249ae1f41f19629a209ce40302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27f60187ddd86d2f8f92304d17ddd50ae57181bd1ed7f50fdf3a495a6b65dc69 0.600000000000 1551629 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": 1078912, "vin": [ { "gen": { "height": 1078902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27f60187ddd86d2f8f92304d17ddd50ae57181bd1ed7f50fdf3a495a6b65dc69" } } ], "extra": [ 1, 80, 206, 59, 28, 38, 233, 153, 177, 140, 16, 177, 186, 92, 229, 128, 129, 100, 126, 115, 65, 36, 154, 225, 244, 31, 25, 98, 154, 32, 156, 228, 3, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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