Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53a1770106978ecf0cc2cde4f2604004a345536731f49e0c4bd1285cb4f2a03

Tx prefix hash: 963a1052fa1c11bb92f587b814e250c3cb3da4cfbff1b0d9188b4599419a3ab1
Tx public key: 2b0b31476c2972b2c471e79c995ed4fa991bd293a3815515063202993ef26b2d
Timestamp: 1710729574 Timestamp [UCT]: 2024-03-18 02:39:34 Age [y:d:h:m:s]: 01:004:16:28:07
Block: 980720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264311 RingCT/type: yes/0
Extra: 012b0b31476c2972b2c471e79c995ed4fa991bd293a3815515063202993ef26b2d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d5ac2ab8b3a456286e24b007c3a346ff72bf7d6da2985ca7e7d124a8e979f1a 0.600000000000 1440801 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": 980730, "vin": [ { "gen": { "height": 980720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d5ac2ab8b3a456286e24b007c3a346ff72bf7d6da2985ca7e7d124a8e979f1a" } } ], "extra": [ 1, 43, 11, 49, 71, 108, 41, 114, 178, 196, 113, 231, 156, 153, 94, 212, 250, 153, 27, 210, 147, 163, 129, 85, 21, 6, 50, 2, 153, 62, 242, 107, 45, 2, 17, 0, 0, 0, 5, 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