Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb656825b781b330861c28449c44eb7a8f815e2e30148e22c285edcd55a55f0

Tx prefix hash: a19278138e6e29ab50f71394e54e0accd15a57327d0275a6c93a246bffc32fd6
Tx public key: d88385d44068ea7ce4b610d6a1305993c7c59161e0b48f6a95ae45c5765e7ddb
Timestamp: 1722329896 Timestamp [UCT]: 2024-07-30 08:58:16 Age [y:d:h:m:s]: 00:234:17:09:22
Block: 1076872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167646 RingCT/type: yes/0
Extra: 01d88385d44068ea7ce4b610d6a1305993c7c59161e0b48f6a95ae45c5765e7ddb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c5eaff10ce690b8cb02fb74090e270377f82f5c54bf8eaab12972c73ba696ef 0.600000000000 1549413 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": 1076882, "vin": [ { "gen": { "height": 1076872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c5eaff10ce690b8cb02fb74090e270377f82f5c54bf8eaab12972c73ba696ef" } } ], "extra": [ 1, 216, 131, 133, 212, 64, 104, 234, 124, 228, 182, 16, 214, 161, 48, 89, 147, 199, 197, 145, 97, 224, 180, 143, 106, 149, 174, 69, 197, 118, 94, 125, 219, 2, 17, 0, 0, 0, 1, 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