Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6448d2a91d61dd55bbb93bf1f1cd534e3ab2cb5f0bfa54e8ee6a9c5834a74b

Tx prefix hash: 8b44f34bd867a9dd805a99cdc31b5b7c90cb6608eb32b51653f17c448f07aaa4
Tx public key: beac4306b1c422f2e02b96c26accf4208319850e3f4fdc5fb136ca61379ac1de
Timestamp: 1762341737 Timestamp [UCT]: 2025-11-05 11:22:17 Age [y:d:h:m:s]: 00:050:14:36:10
Block: 1405456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36245 RingCT/type: yes/0
Extra: 01beac4306b1c422f2e02b96c26accf4208319850e3f4fdc5fb136ca61379ac1de02110000000adf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6461eeeb0e82d68c68d80c2a477ad1473017e164c03422dd79d9c4aa40a33686 0.600000000000 1893827 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": 1405466, "vin": [ { "gen": { "height": 1405456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6461eeeb0e82d68c68d80c2a477ad1473017e164c03422dd79d9c4aa40a33686" } } ], "extra": [ 1, 190, 172, 67, 6, 177, 196, 34, 242, 224, 43, 150, 194, 106, 204, 244, 32, 131, 25, 133, 14, 63, 79, 220, 95, 177, 54, 202, 97, 55, 154, 193, 222, 2, 17, 0, 0, 0, 10, 223, 90, 36, 122, 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