Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c08e2522b84279482360a62fc27cff15269edbf1bb9b8d348450aaba4fb1660c

Tx prefix hash: 660a9a69350d11692185d8e0d21ce9fe331d815dc8cae8f6cc955114cdf27c46
Tx public key: c3511f82ffda2cf147883eb2d1cdc4dfa05a91f8eba6c26c34ad9bcc54e82262
Timestamp: 1714694765 Timestamp [UCT]: 2024-05-03 00:06:05 Age [y:d:h:m:s]: 01:203:14:01:10
Block: 1013579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404142 RingCT/type: yes/0
Extra: 01c3511f82ffda2cf147883eb2d1cdc4dfa05a91f8eba6c26c34ad9bcc54e822620211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eda0f2cbd136636397d3c7073def8675fdf0f9041dcae4bdb2dc4b204eb7cb7 0.600000000000 1476434 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": 1013589, "vin": [ { "gen": { "height": 1013579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eda0f2cbd136636397d3c7073def8675fdf0f9041dcae4bdb2dc4b204eb7cb7" } } ], "extra": [ 1, 195, 81, 31, 130, 255, 218, 44, 241, 71, 136, 62, 178, 209, 205, 196, 223, 160, 90, 145, 248, 235, 166, 194, 108, 52, 173, 155, 204, 84, 232, 34, 98, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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