Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4785edbf1bbf7a35d36b4cecb951814f8cece315f2d762b7e021db4cdfec8413

Tx prefix hash: f938bd0880b8f59beaaec359e870b801c85d643ccb2bbf3719322565b64b93ac
Tx public key: 3619d13a0b4714e01d504b921174fccd96ba4e9ccbe536d95c82e0040cfa7f37
Timestamp: 1764229526 Timestamp [UCT]: 2025-11-27 07:45:26 Age [y:d:h:m:s]: 00:057:12:43:49
Block: 1421115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41004 RingCT/type: yes/0
Extra: 013619d13a0b4714e01d504b921174fccd96ba4e9ccbe536d95c82e0040cfa7f37021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd2347b5a5fa4f944d8a3ee5d5933d9c29e94c6fb904f6c6502852b95d61a28e 0.600000000000 1909670 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": 1421125, "vin": [ { "gen": { "height": 1421115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd2347b5a5fa4f944d8a3ee5d5933d9c29e94c6fb904f6c6502852b95d61a28e" } } ], "extra": [ 1, 54, 25, 209, 58, 11, 71, 20, 224, 29, 80, 75, 146, 17, 116, 252, 205, 150, 186, 78, 156, 203, 229, 54, 217, 92, 130, 224, 4, 12, 250, 127, 55, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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