Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 046d6f3006cce855c07f94d6d9c0302b0962e8cf4a7458332c64ed8d9af9cd06

Tx prefix hash: 3030fa45ba9d7d28d9b02b815146fb943441eab6797df05e64d24bebb82ee7a3
Tx public key: 90aa7ab4a20c1dd9e99131c0709dcc4bfd2a3986f8c6cf8b758833554b308994
Timestamp: 1761575269 Timestamp [UCT]: 2025-10-27 14:27:49 Age [y:d:h:m:s]: 00:014:08:54:49
Block: 1399131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10272 RingCT/type: yes/0
Extra: 0190aa7ab4a20c1dd9e99131c0709dcc4bfd2a3986f8c6cf8b758833554b3089940211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55a0fd8fcee9332b337a66b020ce027b6006dfb97fe6ae3fef443e75ec2e867b 0.600000000000 1887436 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": 1399141, "vin": [ { "gen": { "height": 1399131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55a0fd8fcee9332b337a66b020ce027b6006dfb97fe6ae3fef443e75ec2e867b" } } ], "extra": [ 1, 144, 170, 122, 180, 162, 12, 29, 217, 233, 145, 49, 192, 112, 157, 204, 75, 253, 42, 57, 134, 248, 198, 207, 139, 117, 136, 51, 85, 75, 48, 137, 148, 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