Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2adcc597b7bca3c13609021ed0307467fbe06cc9e4cb8010f65a62299a0df1

Tx prefix hash: 3f8c42169bda0bcaf74a253ead03cc369c7893ebfec10ca42beb0b1209de23bd
Tx public key: 00c35a7c8349c6d2d58d317e999a802c6f2fc0f6ab7e7be1b3c390c1017cc460
Timestamp: 1725926159 Timestamp [UCT]: 2024-09-09 23:55:59 Age [y:d:h:m:s]: 01:059:10:44:01
Block: 1106697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300895 RingCT/type: yes/0
Extra: 0100c35a7c8349c6d2d58d317e999a802c6f2fc0f6ab7e7be1b3c390c1017cc46002110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c4b0d67e4fc2498ae65c21d1965d60fd043785d765bd95b02017bd52be4ef82 0.600000000000 1584298 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": 1106707, "vin": [ { "gen": { "height": 1106697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c4b0d67e4fc2498ae65c21d1965d60fd043785d765bd95b02017bd52be4ef82" } } ], "extra": [ 1, 0, 195, 90, 124, 131, 73, 198, 210, 213, 141, 49, 126, 153, 154, 128, 44, 111, 47, 192, 246, 171, 126, 123, 225, 179, 195, 144, 193, 1, 124, 196, 96, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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