Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc77a1c5647cf23e6f5f24509f3d7b61d76e705594959f1de7208e6fb8b3cfdc

Tx prefix hash: 4ab7e18c8bdcdfe3ccbe84816f0283912beb3db47d456325e01326ca96fef121
Tx public key: 5f1c758e35481322d73c1e3f92a8a3787897c5e98822ad33c8623218e9b456e9
Timestamp: 1583564749 Timestamp [UCT]: 2020-03-07 07:05:49 Age [y:d:h:m:s]: 04:296:01:26:19
Block: 78067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106106 RingCT/type: yes/0
Extra: 015f1c758e35481322d73c1e3f92a8a3787897c5e98822ad33c8623218e9b456e90211000000128a2ee0d9000000000000000000

1 output(s) for total of 338.323694468000 dcy

stealth address amount amount idx
00: 0f0c42851dc9bf0ea9bc08561cfa410a76b38afd76bdcca69c2e6f98a617e07a 338.323694468000 143368 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": 78077, "vin": [ { "gen": { "height": 78067 } } ], "vout": [ { "amount": 338323694468, "target": { "key": "0f0c42851dc9bf0ea9bc08561cfa410a76b38afd76bdcca69c2e6f98a617e07a" } } ], "extra": [ 1, 95, 28, 117, 142, 53, 72, 19, 34, 215, 60, 30, 63, 146, 168, 163, 120, 120, 151, 197, 233, 136, 34, 173, 51, 200, 98, 50, 24, 233, 180, 86, 233, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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