Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa127ae5a333ec35602ff56a678e4858c401949e1733f4b721a05776bcc3f2d

Tx prefix hash: 4e75453b619f6e580516a9c338e5211e000c954bda18c1b308c69256b526962a
Tx public key: c0c5c99a843e64ff44f8f75a6d3bc36e84af464d107e7b68f6ef276458977b28
Timestamp: 1707364094 Timestamp [UCT]: 2024-02-08 03:48:14 Age [y:d:h:m:s]: 01:284:13:45:09
Block: 952788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462175 RingCT/type: yes/0
Extra: 01c0c5c99a843e64ff44f8f75a6d3bc36e84af464d107e7b68f6ef276458977b2802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8cce01b726f8f8ae5a59bed92aa1aa9fa45118fa51999be113ff6cb1f73b374 0.600000000000 1411918 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": 952798, "vin": [ { "gen": { "height": 952788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8cce01b726f8f8ae5a59bed92aa1aa9fa45118fa51999be113ff6cb1f73b374" } } ], "extra": [ 1, 192, 197, 201, 154, 132, 62, 100, 255, 68, 248, 247, 90, 109, 59, 195, 110, 132, 175, 70, 77, 16, 126, 123, 104, 246, 239, 39, 100, 88, 151, 123, 40, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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