Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849625cf924f1652d5f2747965f6decf38edcc417366ee286ad0dc1a5111ad7d

Tx prefix hash: 0a33615e1a19c6438508f374c238fe164cad0a9e2227235218a6a224c1b17e59
Tx public key: 4e5d2aac14c70d5090498d5fe519816bfef0b25b439ad3c27b8d0b7f252e69ce
Timestamp: 1717229472 Timestamp [UCT]: 2024-06-01 08:11:12 Age [y:d:h:m:s]: 00:297:19:55:55
Block: 1034595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212830 RingCT/type: yes/0
Extra: 014e5d2aac14c70d5090498d5fe519816bfef0b25b439ad3c27b8d0b7f252e69ce02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8adf313e59b305080d336930d03ab85eaceba0fa23fd797005ec6d235ad89ee9 0.600000000000 1503108 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": 1034605, "vin": [ { "gen": { "height": 1034595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8adf313e59b305080d336930d03ab85eaceba0fa23fd797005ec6d235ad89ee9" } } ], "extra": [ 1, 78, 93, 42, 172, 20, 199, 13, 80, 144, 73, 141, 95, 229, 25, 129, 107, 254, 240, 178, 91, 67, 154, 211, 194, 123, 141, 11, 127, 37, 46, 105, 206, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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