Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb035eee31f5ef13766706d3c4ced2bc337fb70f2ded98c226dd1f5b035a499

Tx prefix hash: aecea38065a0938a62107e7a50df3c099ce53f7c8cc5ba01221ffab08e275c56
Tx public key: f015c8c923dee3e9170cd2c36b475a710c88dc4129652484b577d3de269b41ae
Timestamp: 1737340335 Timestamp [UCT]: 2025-01-20 02:32:15 Age [y:d:h:m:s]: 00:053:22:10:43
Block: 1201116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38367 RingCT/type: yes/0
Extra: 01f015c8c923dee3e9170cd2c36b475a710c88dc4129652484b577d3de269b41ae021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e26229210e6ab49051d83186c8251b625cd9383e880b5f6eaacc8462281712b6 0.600000000000 1687765 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": 1201126, "vin": [ { "gen": { "height": 1201116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e26229210e6ab49051d83186c8251b625cd9383e880b5f6eaacc8462281712b6" } } ], "extra": [ 1, 240, 21, 200, 201, 35, 222, 227, 233, 23, 12, 210, 195, 107, 71, 90, 113, 12, 136, 220, 65, 41, 101, 36, 132, 181, 119, 211, 222, 38, 155, 65, 174, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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