Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53cbac4f61176ede3b371f47f3595944f6fd5bf0a27a501a6d5af83abfabf645

Tx prefix hash: af461e7ea3035f960847d70418ed280f79eb4c99e1438ce30abf969e3af21470
Tx public key: e5ddf251789626cb7d64cbf8de5224506d41e5c8034d71c3b40603e42f58b545
Timestamp: 1580118629 Timestamp [UCT]: 2020-01-27 09:50:29 Age [y:d:h:m:s]: 05:103:01:04:04
Block: 53899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224504 RingCT/type: yes/0
Extra: 01e5ddf251789626cb7d64cbf8de5224506d41e5c8034d71c3b40603e42f58b5450211000000032264afe6000000000000000000

1 output(s) for total of 406.828215516000 dcy

stealth address amount amount idx
00: df43a6b3a5c181b2eb86ea9075e3482d59af8bb0c7c2b82f7523830c6982dd58 406.828215516000 99868 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": 53909, "vin": [ { "gen": { "height": 53899 } } ], "vout": [ { "amount": 406828215516, "target": { "key": "df43a6b3a5c181b2eb86ea9075e3482d59af8bb0c7c2b82f7523830c6982dd58" } } ], "extra": [ 1, 229, 221, 242, 81, 120, 150, 38, 203, 125, 100, 203, 248, 222, 82, 36, 80, 109, 65, 229, 200, 3, 77, 113, 195, 180, 6, 3, 228, 47, 88, 181, 69, 2, 17, 0, 0, 0, 3, 34, 100, 175, 230, 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