Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58dc576721b5e6a5f1fe3a3e03106de9ee5f59748a99257595ce69063d1b066

Tx prefix hash: e3be066053872e7be25d809dbe700c7f6b7ef07fba2a7add76ee537727f302b4
Tx public key: 66485ca460d273ea1473e2af575f12dae3856f4f36bbba5012961d32bfcefb49
Timestamp: 1712504615 Timestamp [UCT]: 2024-04-07 15:43:35 Age [y:d:h:m:s]: 01:070:14:05:54
Block: 995382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311368 RingCT/type: yes/0
Extra: 0166485ca460d273ea1473e2af575f12dae3856f4f36bbba5012961d32bfcefb490211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ec1ab3e3fbbff9cb76ad5bb9a2b08bea0d51f4f1deec95dcd7a2abcaed07c36 0.600000000000 1455790 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": 995392, "vin": [ { "gen": { "height": 995382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ec1ab3e3fbbff9cb76ad5bb9a2b08bea0d51f4f1deec95dcd7a2abcaed07c36" } } ], "extra": [ 1, 102, 72, 92, 164, 96, 210, 115, 234, 20, 115, 226, 175, 87, 95, 18, 218, 227, 133, 111, 79, 54, 187, 186, 80, 18, 150, 29, 50, 191, 206, 251, 73, 2, 17, 0, 0, 0, 5, 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