Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d373a3c4ab0aed4b6fe0ea0ced12d98bb764c3cb4d6c176926e868e2354f5cd

Tx prefix hash: 5fc8c48c42c0a862f9c0023c6f260e480a822eecbaea6efcc3f315e8c34c1c55
Tx public key: d65d768c801a6f07e4d202d782afa96774ef4610be97e6544763fec2613be7e3
Timestamp: 1738880832 Timestamp [UCT]: 2025-02-06 22:27:12 Age [y:d:h:m:s]: 00:330:23:13:10
Block: 1213659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234369 RingCT/type: yes/0
Extra: 01d65d768c801a6f07e4d202d782afa96774ef4610be97e6544763fec2613be7e3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 913b4e376fd1378902675b50493ef4806d53a6c6bd39c0a05a44143393ad8b41 0.600000000000 1700440 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": 1213669, "vin": [ { "gen": { "height": 1213659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "913b4e376fd1378902675b50493ef4806d53a6c6bd39c0a05a44143393ad8b41" } } ], "extra": [ 1, 214, 93, 118, 140, 128, 26, 111, 7, 228, 210, 2, 215, 130, 175, 169, 103, 116, 239, 70, 16, 190, 151, 230, 84, 71, 99, 254, 194, 97, 59, 231, 227, 2, 17, 0, 0, 0, 4, 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