Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05000d46fcfe01d5cdc8a2ed83a0c9caa8772d2b26498274b6b3c211cf7f5361

Tx prefix hash: d5fc6e5e5315c86f5ab3d6b0ec1574815b04a18ff14316c53e959f940794a21c
Tx public key: 647aa1d9f7dd82117c31db4c3144279a2429a42243a63bb57e6b461cefdd0565
Timestamp: 1734235580 Timestamp [UCT]: 2024-12-15 04:06:20 Age [y:d:h:m:s]: 00:094:13:59:46
Block: 1175484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67381 RingCT/type: yes/0
Extra: 01647aa1d9f7dd82117c31db4c3144279a2429a42243a63bb57e6b461cefdd0565021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a821032b28a1d3bb58b31545bf83c4110e75beb3c4c21d928f43f560dd321e1c 0.600000000000 1661769 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": 1175494, "vin": [ { "gen": { "height": 1175484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a821032b28a1d3bb58b31545bf83c4110e75beb3c4c21d928f43f560dd321e1c" } } ], "extra": [ 1, 100, 122, 161, 217, 247, 221, 130, 17, 124, 49, 219, 76, 49, 68, 39, 154, 36, 41, 164, 34, 67, 166, 59, 181, 126, 107, 70, 28, 239, 221, 5, 101, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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