Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c3299e03290517c23c5e20f6a3ce9aa7a9d29e9b41d2f6ffb058ed33e7026c

Tx prefix hash: 0fef838168981d81c9a0d3272bbd8e6402f3f58035aedb6ad6ece054b67a39e1
Tx public key: 85fb35b319418c3dd01650d6cfff977c0ec93097f4b21b9a5e3c9c7636092bf0
Timestamp: 1674975612 Timestamp [UCT]: 2023-01-29 07:00:12 Age [y:d:h:m:s]: 02:027:05:43:10
Block: 685157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541066 RingCT/type: yes/0
Extra: 0185fb35b319418c3dd01650d6cfff977c0ec93097f4b21b9a5e3c9c7636092bf002110000000175e3f0e9000000000000000000

1 output(s) for total of 3.294506523000 dcy

stealth address amount amount idx
00: 4a4a6fae4b83f32a6a11dc47b1898a7961924b0bc588918a84d82d41b4abf452 3.294506523000 1127446 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": 685167, "vin": [ { "gen": { "height": 685157 } } ], "vout": [ { "amount": 3294506523, "target": { "key": "4a4a6fae4b83f32a6a11dc47b1898a7961924b0bc588918a84d82d41b4abf452" } } ], "extra": [ 1, 133, 251, 53, 179, 25, 65, 140, 61, 208, 22, 80, 214, 207, 255, 151, 124, 14, 201, 48, 151, 244, 178, 27, 154, 94, 60, 156, 118, 54, 9, 43, 240, 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