Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9578ec20ad00715dc281c6bbc77ae706c58415d48a468055cc22818900f3d6a0

Tx prefix hash: 0e7d301246abad433d90292c65cb73213c56cbd613d8d3c923d8639f2ad65c19
Tx public key: ee69657ae60b418a8a69025bc1e01cf6eb47eba056de2ca136c301d73923f582
Timestamp: 1686292531 Timestamp [UCT]: 2023-06-09 06:35:31 Age [y:d:h:m:s]: 01:361:15:17:27
Block: 778361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519687 RingCT/type: yes/0
Extra: 01ee69657ae60b418a8a69025bc1e01cf6eb47eba056de2ca136c301d73923f582021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.617957299000 dcy

stealth address amount amount idx
00: 5f0604d8eeb5c548faa1f2ef0fe9344b1fa8b0681d1e3f3c318db4e78534f50f 1.617957299000 1227982 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": 778371, "vin": [ { "gen": { "height": 778361 } } ], "vout": [ { "amount": 1617957299, "target": { "key": "5f0604d8eeb5c548faa1f2ef0fe9344b1fa8b0681d1e3f3c318db4e78534f50f" } } ], "extra": [ 1, 238, 105, 101, 122, 230, 11, 65, 138, 138, 105, 2, 91, 193, 224, 28, 246, 235, 71, 235, 160, 86, 222, 44, 161, 54, 195, 1, 215, 57, 35, 245, 130, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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