Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38d267fa6aa03e93a2fcfe668eee01cb077073bd4c642d1eff3c9596f920809d

Tx prefix hash: 31049b3ba3cacfd3c66263f0b68b04ef2b38ab4075a2212e7b237cc91d937786
Tx public key: e292cf7c9b6b30a4caf8d07cc4f1a79a89f7b40b67a781fd1f4da6e28e251041
Timestamp: 1766202306 Timestamp [UCT]: 2025-12-20 03:45:06 Age [y:d:h:m:s]: 00:001:15:23:19
Block: 1437464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1166 RingCT/type: yes/0
Extra: 01e292cf7c9b6b30a4caf8d07cc4f1a79a89f7b40b67a781fd1f4da6e28e251041021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ff3f9434969afc17a57b7cbf0a55cd5c4a96c78acbee54cb433fcfe3a45c81a 0.600000000000 1926273 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": 1437474, "vin": [ { "gen": { "height": 1437464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ff3f9434969afc17a57b7cbf0a55cd5c4a96c78acbee54cb433fcfe3a45c81a" } } ], "extra": [ 1, 226, 146, 207, 124, 155, 107, 48, 164, 202, 248, 208, 124, 196, 241, 167, 154, 137, 247, 180, 11, 103, 167, 129, 253, 31, 77, 166, 226, 142, 37, 16, 65, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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