Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44a80b4401238db224b2c3f1c5adbedab98cdaeb9d6f344a7c3e9fb28eb0826

Tx prefix hash: f3048cd253e8485bf8ee71c6a06f7c260f21ef9eb76d54942ae28eae36c932d5
Tx public key: 846f5ce2840b0199c3c5f88dad59265dea5e1b62dff24659fec791a379388f44
Timestamp: 1688986504 Timestamp [UCT]: 2023-07-10 10:55:04 Age [y:d:h:m:s]: 01:191:19:04:29
Block: 800697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398420 RingCT/type: yes/0
Extra: 01846f5ce2840b0199c3c5f88dad59265dea5e1b62dff24659fec791a379388f440211000000014b8f5122000000000000000000

1 output(s) for total of 1.364453007000 dcy

stealth address amount amount idx
00: 4e8b135d0c2691cef6a0802b885413a6e969f16fb66cbefde31969e196ea7d51 1.364453007000 1251760 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": 800707, "vin": [ { "gen": { "height": 800697 } } ], "vout": [ { "amount": 1364453007, "target": { "key": "4e8b135d0c2691cef6a0802b885413a6e969f16fb66cbefde31969e196ea7d51" } } ], "extra": [ 1, 132, 111, 92, 226, 132, 11, 1, 153, 195, 197, 248, 141, 173, 89, 38, 93, 234, 94, 27, 98, 223, 242, 70, 89, 254, 199, 145, 163, 121, 56, 143, 68, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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