Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be9df6f5b856cd82808a397ec3057c24bd29866dff9a5a8f859f78931b900477

Tx prefix hash: 4534681c3845357b5020c6c5a9d1c0e3c6aa9472c9fda7b57389da23d79c1e11
Tx public key: 2c8205e2df7827da48821b71f5671f62561abf30ad9fb79aeaf85e364fffc66b
Timestamp: 1721934910 Timestamp [UCT]: 2024-07-25 19:15:10 Age [y:d:h:m:s]: 00:252:06:38:23
Block: 1073595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180202 RingCT/type: yes/0
Extra: 012c8205e2df7827da48821b71f5671f62561abf30ad9fb79aeaf85e364fffc66b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b88b97ae73963ba41a65de6e367fdcd1e63617056f7f5adbd0215c522b96a0d6 0.600000000000 1546100 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": 1073605, "vin": [ { "gen": { "height": 1073595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b88b97ae73963ba41a65de6e367fdcd1e63617056f7f5adbd0215c522b96a0d6" } } ], "extra": [ 1, 44, 130, 5, 226, 223, 120, 39, 218, 72, 130, 27, 113, 245, 103, 31, 98, 86, 26, 191, 48, 173, 159, 183, 154, 234, 248, 94, 54, 79, 255, 198, 107, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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