Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e3f34aff66fa8c0857d89f526d43367a53d4ff3bc2bd61a396b90c261ba8613

Tx prefix hash: 9747da6450a933dbbabdd5044564db2723bca76d71da50de44c38fd48c4fdc92
Tx public key: 823c35a8424b24d218431a98dc635c452c612bc33fcb6d64c54c32b483ab213e
Timestamp: 1700946098 Timestamp [UCT]: 2023-11-25 21:01:38 Age [y:d:h:m:s]: 01:143:15:28:44
Block: 899588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363833 RingCT/type: yes/0
Extra: 01823c35a8424b24d218431a98dc635c452c612bc33fcb6d64c54c32b483ab213e021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.641640108000 dcy

stealth address amount amount idx
00: bdc72a9ecca3063d1eb2eb807a0a44bce10eff985db573724d7fd83136b3adb1 0.641640108000 1356047 of 0

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": 899598, "vin": [ { "gen": { "height": 899588 } } ], "vout": [ { "amount": 641640108, "target": { "key": "bdc72a9ecca3063d1eb2eb807a0a44bce10eff985db573724d7fd83136b3adb1" } } ], "extra": [ 1, 130, 60, 53, 168, 66, 75, 36, 210, 24, 67, 26, 152, 220, 99, 92, 69, 44, 97, 43, 195, 63, 203, 109, 100, 197, 76, 50, 180, 131, 171, 33, 62, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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