Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a5bd0a1ad1428bdb5ac326b3ef7e65aebee6731a7ee2b30f4e57adb97293af

Tx prefix hash: 0c68592e33b8b985d80489c79666386a3f053b8c663f0aa6d5f51eb87b601fae
Tx public key: cabde930b4ec5cc76df66ff4c7342de5a2949fc78933fd0584a32092bee3f304
Timestamp: 1734073144 Timestamp [UCT]: 2024-12-13 06:59:04 Age [y:d:h:m:s]: 00:103:14:37:51
Block: 1174142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73797 RingCT/type: yes/0
Extra: 01cabde930b4ec5cc76df66ff4c7342de5a2949fc78933fd0584a32092bee3f304021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc2c5b2a64b5942934a28737ee56df143bf9b4c4a576e8ad92cc46ecf10d2705 0.600000000000 1660257 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": 1174152, "vin": [ { "gen": { "height": 1174142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc2c5b2a64b5942934a28737ee56df143bf9b4c4a576e8ad92cc46ecf10d2705" } } ], "extra": [ 1, 202, 189, 233, 48, 180, 236, 92, 199, 109, 246, 111, 244, 199, 52, 45, 229, 162, 148, 159, 199, 137, 51, 253, 5, 132, 163, 32, 146, 190, 227, 243, 4, 2, 17, 0, 0, 0, 6, 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