Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 226cffdfb828e6a81a4600d62704d37ea88c02e3c91a623674a36e571989334c

Tx prefix hash: 74c39a70ad6ea5111a042b2d5beb96f25ef597facb5b9b4089c1eeec3eb49dd0
Tx public key: 0a6e475888f249b49a2bc9a210a9b08e306ab9e3dc47c391d9ac4acbad9faa11
Timestamp: 1732892977 Timestamp [UCT]: 2024-11-29 15:09:37 Age [y:d:h:m:s]: 00:116:23:20:29
Block: 1164349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83386 RingCT/type: yes/0
Extra: 010a6e475888f249b49a2bc9a210a9b08e306ab9e3dc47c391d9ac4acbad9faa110211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61336b6900f146fc038aabc1b693fe71651d2ba522874b001b04267652a55178 0.600000000000 1650022 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": 1164359, "vin": [ { "gen": { "height": 1164349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61336b6900f146fc038aabc1b693fe71651d2ba522874b001b04267652a55178" } } ], "extra": [ 1, 10, 110, 71, 88, 136, 242, 73, 180, 154, 43, 201, 162, 16, 169, 176, 142, 48, 106, 185, 227, 220, 71, 195, 145, 217, 172, 74, 203, 173, 159, 170, 17, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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