Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21c26b64710cb6de75f088769d6460cab4abcbb1bc3d96f228dbbc8a51f95445

Tx prefix hash: 198dcd2190776a88c71188c9f977cd15310acb8217f30ef667599d6613171f6b
Tx public key: c94cef85f36480dff99a45f3eb89d9107b828c7af5c8993f7566e54a3a6a29e6
Timestamp: 1728586246 Timestamp [UCT]: 2024-10-10 18:50:46 Age [y:d:h:m:s]: 01:032:16:20:00
Block: 1128739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281734 RingCT/type: yes/0
Extra: 01c94cef85f36480dff99a45f3eb89d9107b828c7af5c8993f7566e54a3a6a29e602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4f6c1dd2f23733b6f4da92157bfdd41f72c3bc4497a9bfb5a14912f07a8e7a 0.600000000000 1611560 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": 1128749, "vin": [ { "gen": { "height": 1128739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4f6c1dd2f23733b6f4da92157bfdd41f72c3bc4497a9bfb5a14912f07a8e7a" } } ], "extra": [ 1, 201, 76, 239, 133, 243, 100, 128, 223, 249, 154, 69, 243, 235, 137, 217, 16, 123, 130, 140, 122, 245, 200, 153, 63, 117, 102, 229, 74, 58, 106, 41, 230, 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