Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde5b1666e6c8c9dbada13edd29f1db690132b8f15868933df59d91fd7b56703

Tx prefix hash: b029b5a6e75c88abc5b26603197dc5c5abfeda0e2839e6455cdd8e540fbabe7c
Tx public key: d83e09a69b670226f40f7062bc4d3a60f4cee95eb13d83aab22fbb8bee2be035
Timestamp: 1751681202 Timestamp [UCT]: 2025-07-05 02:06:42 Age [y:d:h:m:s]: 00:126:22:32:56
Block: 1318979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89028 RingCT/type: yes/0
Extra: 01d83e09a69b670226f40f7062bc4d3a60f4cee95eb13d83aab22fbb8bee2be0350211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61693bb810c5e320fa9f3e935fd02c43ff6ce60837ed532caa66d49dfadde58d 0.600000000000 1806668 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": 1318989, "vin": [ { "gen": { "height": 1318979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61693bb810c5e320fa9f3e935fd02c43ff6ce60837ed532caa66d49dfadde58d" } } ], "extra": [ 1, 216, 62, 9, 166, 155, 103, 2, 38, 244, 15, 112, 98, 188, 77, 58, 96, 244, 206, 233, 94, 177, 61, 131, 170, 178, 47, 187, 139, 238, 43, 224, 53, 2, 17, 0, 0, 0, 3, 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