Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a08782d3dba69a07cc93e1863ffeafb94ffb63991ca9d8cb2f97e384a543b3c

Tx prefix hash: 701a9d88626627a2ad94a1cfe94d1e5289ba4887f9e6011fa05931c42acdd877
Tx public key: 61b89b314cd641ca727d526ae7d6f1194a4c12f73513431b0c0c92468599d491
Timestamp: 1719438498 Timestamp [UCT]: 2024-06-26 21:48:18 Age [y:d:h:m:s]: 00:306:00:47:04
Block: 1052894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218704 RingCT/type: yes/0
Extra: 0161b89b314cd641ca727d526ae7d6f1194a4c12f73513431b0c0c92468599d49102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b2a589224fbe80a3ed7bdbac959ffa0979c61428928bb0ea7da2c28b0dc0a40 0.600000000000 1523233 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": 1052904, "vin": [ { "gen": { "height": 1052894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2a589224fbe80a3ed7bdbac959ffa0979c61428928bb0ea7da2c28b0dc0a40" } } ], "extra": [ 1, 97, 184, 155, 49, 76, 214, 65, 202, 114, 125, 82, 106, 231, 214, 241, 25, 74, 76, 18, 247, 53, 19, 67, 27, 12, 12, 146, 70, 133, 153, 212, 145, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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