Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8070373dc1f98725c155fcef952183d66224350ba5bc3b5d9b82c9d684de0a

Tx prefix hash: 5dc665c6800cb311a5d0ce003aa0e04f9f748297d65dd5b63f7b093415a525c9
Tx public key: c1ff67a55cb863641a8b7ec685ea54fad96be4bfff003bac6b1de52489a7218e
Timestamp: 1753293760 Timestamp [UCT]: 2025-07-23 18:02:40 Age [y:d:h:m:s]: 00:166:08:04:33
Block: 1331813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117776 RingCT/type: yes/0
Extra: 01c1ff67a55cb863641a8b7ec685ea54fad96be4bfff003bac6b1de52489a7218e02110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443dfaecf66df98eac878cdeb2b21a4e7f7e39e6a4a8c7197622327acc112286 0.600000000000 1819610 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": 1331823, "vin": [ { "gen": { "height": 1331813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443dfaecf66df98eac878cdeb2b21a4e7f7e39e6a4a8c7197622327acc112286" } } ], "extra": [ 1, 193, 255, 103, 165, 92, 184, 99, 100, 26, 139, 126, 198, 133, 234, 84, 250, 217, 107, 228, 191, 255, 0, 59, 172, 107, 29, 229, 36, 137, 167, 33, 142, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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