Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be10404491cb0941515bae1dc1f77561d654b81db7a86e6adb41a7c2fc285b30

Tx prefix hash: 7da2147c42c9840931e73fb1bd5bcbcf7a75384d64e6d7bd0c4fbf639a73c929
Tx public key: e447a8b2d02a56e1430ac92aaf9a70e58000fd9209d2ffe3805922c78000db06
Timestamp: 1734204385 Timestamp [UCT]: 2024-12-14 19:26:25 Age [y:d:h:m:s]: 00:186:10:29:00
Block: 1175227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132920 RingCT/type: yes/0
Extra: 01e447a8b2d02a56e1430ac92aaf9a70e58000fd9209d2ffe3805922c78000db060211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff55882bd19c1de8d0d4e0c47c8154b5872f81ec52bec913f8016d31c1e941e5 0.600000000000 1661478 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": 1175237, "vin": [ { "gen": { "height": 1175227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff55882bd19c1de8d0d4e0c47c8154b5872f81ec52bec913f8016d31c1e941e5" } } ], "extra": [ 1, 228, 71, 168, 178, 208, 42, 86, 225, 67, 10, 201, 42, 175, 154, 112, 229, 128, 0, 253, 146, 9, 210, 255, 227, 128, 89, 34, 199, 128, 0, 219, 6, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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