Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2878152815127ab76d939b5a87973c35aadb2e9e6874b76fba0e530f000a2eb6

Tx prefix hash: fc26ba9f8b584c65d21f548ab08b0aaace2286a1ce67f1ad6a1b88c89fa082bb
Tx public key: a41186f0af49640b5b33034015af3c132830abd30a7e1a9f6ce3fb7646732156
Timestamp: 1644469284 Timestamp [UCT]: 2022-02-10 05:01:24 Age [y:d:h:m:s]: 03:268:03:52:19
Block: 435469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 969210 RingCT/type: yes/0
Extra: 01a41186f0af49640b5b33034015af3c132830abd30a7e1a9f6ce3fb764673215602110000000537cb3088000000000000000000

1 output(s) for total of 22.136590503000 dcy

stealth address amount amount idx
00: 0d6b654022ef45adac303922aa8ee8d64b46c9dc105a90ca2af61f75ce0d7002 22.136590503000 846666 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": 435479, "vin": [ { "gen": { "height": 435469 } } ], "vout": [ { "amount": 22136590503, "target": { "key": "0d6b654022ef45adac303922aa8ee8d64b46c9dc105a90ca2af61f75ce0d7002" } } ], "extra": [ 1, 164, 17, 134, 240, 175, 73, 100, 11, 91, 51, 3, 64, 21, 175, 60, 19, 40, 48, 171, 211, 10, 126, 26, 159, 108, 227, 251, 118, 70, 115, 33, 86, 2, 17, 0, 0, 0, 5, 55, 203, 48, 136, 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