Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f66a90ff468830b61a33217019f5ae91c0e070457d5faebb631e505faf96c28d

Tx prefix hash: 6c2593b6fb94e343c5c6be9ad47bc95a24f0de04dca3b341fc6f5acad100c13d
Tx public key: c743fd6d207323e3d353af3deff35c5b320774b5404a0bef549ed197994b95c7
Timestamp: 1694870795 Timestamp [UCT]: 2023-09-16 13:26:35 Age [y:d:h:m:s]: 01:250:13:16:33
Block: 849411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440203 RingCT/type: yes/0
Extra: 01c743fd6d207323e3d353af3deff35c5b320774b5404a0bef549ed197994b95c702110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.940911566000 dcy

stealth address amount amount idx
00: 035895c92ecaefb5c321d3976fbdc893f848e0250a39dcc47bcad6271f209f50 0.940911566000 1303075 of 0

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": 849421, "vin": [ { "gen": { "height": 849411 } } ], "vout": [ { "amount": 940911566, "target": { "key": "035895c92ecaefb5c321d3976fbdc893f848e0250a39dcc47bcad6271f209f50" } } ], "extra": [ 1, 199, 67, 253, 109, 32, 115, 35, 227, 211, 83, 175, 61, 239, 243, 92, 91, 50, 7, 116, 181, 64, 74, 11, 239, 84, 158, 209, 151, 153, 75, 149, 199, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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