Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65719e69a7cdcaef91c4f9ed3d5df6f2b8a592acb3007cd4956b0b4705d9f924

Tx prefix hash: 4f8d0bf6a3695e8ca2149631f10fd34dfe5562e70f9f1970d63926386e22c790
Tx public key: aec0da30ad91d6aa5d912522ae9109a9eecd2f5bf0e35b763093fa1b0c8c898b
Timestamp: 1724328281 Timestamp [UCT]: 2024-08-22 12:04:41 Age [y:d:h:m:s]: 00:242:18:55:19
Block: 1093456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173378 RingCT/type: yes/0
Extra: 01aec0da30ad91d6aa5d912522ae9109a9eecd2f5bf0e35b763093fa1b0c8c898b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017600aaea6146a27a0fd3bd75cc7c14c491aebfaac342159e3ff4be15b4a739 0.600000000000 1568403 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": 1093466, "vin": [ { "gen": { "height": 1093456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017600aaea6146a27a0fd3bd75cc7c14c491aebfaac342159e3ff4be15b4a739" } } ], "extra": [ 1, 174, 192, 218, 48, 173, 145, 214, 170, 93, 145, 37, 34, 174, 145, 9, 169, 238, 205, 47, 91, 240, 227, 91, 118, 48, 147, 250, 27, 12, 140, 137, 139, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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