Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b5e66d9bb7423ead103c548d08b0765ded0df674496b565f810848b4f8950aa

Tx prefix hash: 44f3c81f5e0f1fad9ef778f8421f0cf8c72ca4889c57cf39995475a784f45ad2
Tx public key: 4034c87d16b4fcd0d089484437406f0a1d28a9769078e0d2221855e5bbd294e3
Timestamp: 1702768555 Timestamp [UCT]: 2023-12-16 23:15:55 Age [y:d:h:m:s]: 01:333:22:08:49
Block: 914693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497523 RingCT/type: yes/0
Extra: 014034c87d16b4fcd0d089484437406f0a1d28a9769078e0d2221855e5bbd294e302110000000933af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5c578c1f862be2d5deb8c6ec3817adaa1e70c477995d323e36f8cc872ec4973 0.600000000000 1372043 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": 914703, "vin": [ { "gen": { "height": 914693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5c578c1f862be2d5deb8c6ec3817adaa1e70c477995d323e36f8cc872ec4973" } } ], "extra": [ 1, 64, 52, 200, 125, 22, 180, 252, 208, 208, 137, 72, 68, 55, 64, 111, 10, 29, 40, 169, 118, 144, 120, 224, 210, 34, 24, 85, 229, 187, 210, 148, 227, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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