Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10ca2b6a34bcd62e4f663dc58204791fbc3d3e5f17e1686e43f69e96ae529e9d

Tx prefix hash: f6f667aa03edbc6c0d8ad039ba149631becc24cb285c333539bcc81c031129d5
Tx public key: 4c57e53376dcbe50862fb065f284e0982ec1406d4ea00346c0cf4d47ec64763a
Timestamp: 1750566062 Timestamp [UCT]: 2025-06-22 04:21:02 Age [y:d:h:m:s]: 00:152:00:19:02
Block: 1310215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106491 RingCT/type: yes/0
Extra: 014c57e53376dcbe50862fb065f284e0982ec1406d4ea00346c0cf4d47ec64763a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6193535edc7174a2a822aacf72e8656cc97346ab85ffe64e5580745c4f2f353 0.600000000000 1797834 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": 1310225, "vin": [ { "gen": { "height": 1310215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6193535edc7174a2a822aacf72e8656cc97346ab85ffe64e5580745c4f2f353" } } ], "extra": [ 1, 76, 87, 229, 51, 118, 220, 190, 80, 134, 47, 176, 101, 242, 132, 224, 152, 46, 193, 64, 109, 78, 160, 3, 70, 192, 207, 77, 71, 236, 100, 118, 58, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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