Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df8bce120118301f6fef0a460cac02c997ec647fd051736cdf02196cf06ee827

Tx prefix hash: 7ffb6ac434d24376fd9d11b96a69d079e2c0d8a86e8cf739c3b5ba609692d409
Tx public key: 2c16df8cf178c41b3232260b2a7b5943d184071ffd727c002c0300146841ba5a
Timestamp: 1763716161 Timestamp [UCT]: 2025-11-21 09:09:21 Age [y:d:h:m:s]: 00:007:16:53:29
Block: 1416840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5536 RingCT/type: yes/0
Extra: 012c16df8cf178c41b3232260b2a7b5943d184071ffd727c002c0300146841ba5a02110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 446a58d6a28ea83b1a9f8b7e09e871c8bffb83976c0cb253bf22cc6e341d47b7 0.600000000000 1905361 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": 1416850, "vin": [ { "gen": { "height": 1416840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446a58d6a28ea83b1a9f8b7e09e871c8bffb83976c0cb253bf22cc6e341d47b7" } } ], "extra": [ 1, 44, 22, 223, 140, 241, 120, 196, 27, 50, 50, 38, 11, 42, 123, 89, 67, 209, 132, 7, 31, 253, 114, 124, 0, 44, 3, 0, 20, 104, 65, 186, 90, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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