Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3dc08c41a3d5481d80fe88b03abe075b9e6ccfd569b2aaf13172132691599f

Tx prefix hash: f06a9d19353fc0c7f4f7beeace970203e726d9afcf771b4a2e0959eb7f2d7b9d
Tx public key: 0e81d6fe894d8dc8196dfc9632c937c546336703687502cb96817a7e896bde0d
Timestamp: 1696179165 Timestamp [UCT]: 2023-10-01 16:52:45 Age [y:d:h:m:s]: 01:241:12:06:30
Block: 860269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433700 RingCT/type: yes/0
Extra: 010e81d6fe894d8dc8196dfc9632c937c546336703687502cb96817a7e896bde0d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.866107362000 dcy

stealth address amount amount idx
00: 2fce261d1f309592c1ab64aa6ec97eaccd4dbee9f3ddb70c1248529bc0f1d087 0.866107362000 1314545 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": 860279, "vin": [ { "gen": { "height": 860269 } } ], "vout": [ { "amount": 866107362, "target": { "key": "2fce261d1f309592c1ab64aa6ec97eaccd4dbee9f3ddb70c1248529bc0f1d087" } } ], "extra": [ 1, 14, 129, 214, 254, 137, 77, 141, 200, 25, 109, 252, 150, 50, 201, 55, 197, 70, 51, 103, 3, 104, 117, 2, 203, 150, 129, 122, 126, 137, 107, 222, 13, 2, 17, 0, 0, 0, 1, 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