Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9d9f7a02ae390a9d8fb7225fce0d7417c5aa6a1ccd20effeca35a7e7acf2ee

Tx prefix hash: df729e36055f56f554c1d1badb73ab577517c82bc94b21f6729ef14dd14c504f
Tx public key: 703864e3ab25f9a2d2b348762fd863ab10742c17687763aa7951b52bcbf1f50a
Timestamp: 1733478557 Timestamp [UCT]: 2024-12-06 09:49:17 Age [y:d:h:m:s]: 00:110:02:17:26
Block: 1169202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78461 RingCT/type: yes/0
Extra: 01703864e3ab25f9a2d2b348762fd863ab10742c17687763aa7951b52bcbf1f50a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8139c1adc6cebe4f377ae41556b18a3eca37a60cb0e876ed0a0a49e7bae825f1 0.600000000000 1654917 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": 1169212, "vin": [ { "gen": { "height": 1169202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8139c1adc6cebe4f377ae41556b18a3eca37a60cb0e876ed0a0a49e7bae825f1" } } ], "extra": [ 1, 112, 56, 100, 227, 171, 37, 249, 162, 210, 179, 72, 118, 47, 216, 99, 171, 16, 116, 44, 23, 104, 119, 99, 170, 121, 81, 181, 43, 203, 241, 245, 10, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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