Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2280c293310f374cc42701d5c5397da6b30f751af4ba15ed41036c7b7c06a533

Tx prefix hash: 704815ce49dfc1638a13b9ca07e30d2a69ddaa365b72bc962acc168701ff1765
Tx public key: b5e8d24f69e632effe8d56b959343f6e13d8e7e3b35ba61031e303a00570cf45
Timestamp: 1708619981 Timestamp [UCT]: 2024-02-22 16:39:41 Age [y:d:h:m:s]: 00:337:11:38:17
Block: 963207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241546 RingCT/type: yes/0
Extra: 01b5e8d24f69e632effe8d56b959343f6e13d8e7e3b35ba61031e303a00570cf450211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6a79c86b67ee6ed0c1e5c3df13ccde25de140c259b282efaad721f851b775d2 0.600000000000 1422908 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": 963217, "vin": [ { "gen": { "height": 963207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6a79c86b67ee6ed0c1e5c3df13ccde25de140c259b282efaad721f851b775d2" } } ], "extra": [ 1, 181, 232, 210, 79, 105, 230, 50, 239, 254, 141, 86, 185, 89, 52, 63, 110, 19, 216, 231, 227, 179, 91, 166, 16, 49, 227, 3, 160, 5, 112, 207, 69, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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