Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d60f548ca997020b53cefda0cb943b3dbeea2a589e328d0eac9160e29a6e93

Tx prefix hash: ed19324acab8f0b4e5afd8ff9d45e5e53ee18edc8fee4b7def2462a7c2aa0e07
Tx public key: 6e98ac285cede45364f2c65ec19239299ab1ab23adf4cd40b0508acd56d7884e
Timestamp: 1707901877 Timestamp [UCT]: 2024-02-14 09:11:17 Age [y:d:h:m:s]: 01:050:01:12:47
Block: 957243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296823 RingCT/type: yes/0
Extra: 016e98ac285cede45364f2c65ec19239299ab1ab23adf4cd40b0508acd56d7884e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0683827ccdb2e1ea412e554e4cedb4e5b7b4f029331de87e1b6544cb1757fa4b 0.600000000000 1416559 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": 957253, "vin": [ { "gen": { "height": 957243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0683827ccdb2e1ea412e554e4cedb4e5b7b4f029331de87e1b6544cb1757fa4b" } } ], "extra": [ 1, 110, 152, 172, 40, 92, 237, 228, 83, 100, 242, 198, 94, 193, 146, 57, 41, 154, 177, 171, 35, 173, 244, 205, 64, 176, 80, 138, 205, 86, 215, 136, 78, 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