Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42ea07534325265dfe1680564af99169bf9e98debc7e33cfa6c9c7a5f2362c60

Tx prefix hash: 3188f4427fb61bab463d9a9769191c10c65f8bf87b0e32dd020258fb7481c56b
Tx public key: c5e952902a01098c48f3dc8614bff22cb0329ab5e169df0a382de94f36d28500
Timestamp: 1681222628 Timestamp [UCT]: 2023-04-11 14:17:08 Age [y:d:h:m:s]: 02:045:05:12:54
Block: 736310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554511 RingCT/type: yes/0
Extra: 01c5e952902a01098c48f3dc8614bff22cb0329ab5e169df0a382de94f36d2850002110000000575e3f0e9000000000000000000

1 output(s) for total of 2.229972649000 dcy

stealth address amount amount idx
00: 39ac8c5dfdf1770737ebe25c91bda86ff10a8840cd1483bb7c8a193b959ebb08 2.229972649000 1182731 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": 736320, "vin": [ { "gen": { "height": 736310 } } ], "vout": [ { "amount": 2229972649, "target": { "key": "39ac8c5dfdf1770737ebe25c91bda86ff10a8840cd1483bb7c8a193b959ebb08" } } ], "extra": [ 1, 197, 233, 82, 144, 42, 1, 9, 140, 72, 243, 220, 134, 20, 191, 242, 44, 176, 50, 154, 181, 225, 105, 223, 10, 56, 45, 233, 79, 54, 210, 133, 0, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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