Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6606abd05546a9b02d6d52f879206f4e4678ee0024611a2e14cfb79ce9ec6f4

Tx prefix hash: a96ae4be9ec8079ef676417a747bc34c7b4a1bbe061ef06b369562e6f6569207
Tx public key: f0fff6bc09bfff5740ca2ddf4d22184a175b5ab8baf65f3791f3ae31471ab4ac
Timestamp: 1734913627 Timestamp [UCT]: 2024-12-23 00:27:07 Age [y:d:h:m:s]: 00:094:23:45:56
Block: 1181113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67627 RingCT/type: yes/0
Extra: 01f0fff6bc09bfff5740ca2ddf4d22184a175b5ab8baf65f3791f3ae31471ab4ac02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63262ccc0caae2a1fef4c30d53fc1740e042cc36dc06235d38909e7c4745c21d 0.600000000000 1667528 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": 1181123, "vin": [ { "gen": { "height": 1181113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63262ccc0caae2a1fef4c30d53fc1740e042cc36dc06235d38909e7c4745c21d" } } ], "extra": [ 1, 240, 255, 246, 188, 9, 191, 255, 87, 64, 202, 45, 223, 77, 34, 24, 74, 23, 91, 90, 184, 186, 246, 95, 55, 145, 243, 174, 49, 71, 26, 180, 172, 2, 17, 0, 0, 0, 10, 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