Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f3a8ebee49770cf02f4bd1b532321d339431fbaec6ab80f7ec31d9baa771de

Tx prefix hash: 2077a1eede16f62faf86649e3c00df0570352a65d602cf10f8770130a5aa9e3d
Tx public key: 2c5781bfe972119820f24448fae64103a0b6d796b96a4fba842282aed2f89238
Timestamp: 1719891701 Timestamp [UCT]: 2024-07-02 03:41:41 Age [y:d:h:m:s]: 00:174:03:18:04
Block: 1056648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124657 RingCT/type: yes/0
Extra: 012c5781bfe972119820f24448fae64103a0b6d796b96a4fba842282aed2f892380211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d70c748f4bf8b90b81f3ff9cee2baafdd7cb711d7cae7cb961ed0f6d64d68c91 0.600000000000 1527065 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": 1056658, "vin": [ { "gen": { "height": 1056648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d70c748f4bf8b90b81f3ff9cee2baafdd7cb711d7cae7cb961ed0f6d64d68c91" } } ], "extra": [ 1, 44, 87, 129, 191, 233, 114, 17, 152, 32, 242, 68, 72, 250, 230, 65, 3, 160, 182, 215, 150, 185, 106, 79, 186, 132, 34, 130, 174, 210, 248, 146, 56, 2, 17, 0, 0, 0, 4, 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